VS2005 Designer problem

[Dino Buljubasic]

I am having a problem when trying to view a form in desing view.
If a form has any error or warning, the design view will not open the
form.

Anybody knows how to fix this error?

Thank you
_dino_

 

[Stoitcho Goutsev \(100\) [C# MVP]]

Dino,

Can't you fix the error or warning? What kind of application is this Web or
WinForms?

 

[Daniel Billingsley]

In researching my problem I found that this is purposeful design for VS2005.
It is meant to eliminate the annyoing problem of controls disappearing when
there was an error in the previous version.

 

[Dino Buljubasic]

I can fix it, it is just that I find it annoying not to be able to see
my form in design view if there is an error. Say, I want to remove a
control from the form that is causing the problem. This was, I have
to fix the problem first, then remove the control.

I am developing a C# win forms app.

Thank you for your help.

 

[Dino Buljubasic]

That might be the case, although I have not found any reference to
that. Contrary, I have found lots of posts complaining about this
annoying feature and according to my research, this is a bug. (google
VS 2005 Designer problem).

Anyways, if you could send me a link to confirm that would be
greatelly appreciated.

_dino_

 

[Bob Grommes]

My experience of the Winforms designer in VS 2005 so far is that it's
rather buggy.

I've encountered the problem you've described, which can sometimes go
away if you just close and restart VS.

I've also seen some code generation problems with the designer. For
example if you have a form in the Foo namespace, and incorporate a user
control that's also in the Foo namespace (call it Foo.ucBar) then the
designer will try to create a new Foo.ucBar and the compiler will
complain that there is no such thing as Foo.Foo.ucBar. You have to
manually remove the "Foo." from the code to get it to compile.
Apparently there is some implicit assumption that a form and a user
control would never be in the same namespace.

I also have had spurious null exception errors when my code deliberately
assigns null as an initial value to an object ... it's like the IDE is
too smart by half and starts making unwarranted assumptions about what's
going on.

None of this is fatal, just extremely annoying and unreassuring, and I'm
sure that large and complex projects will surface more of this nonsense
and teach me new naughty words in the coming weeks and months.

--Bob

 

[Daniel Billingsley]

The part that is apparently designed functionality is not trying to load the
form (ignoring the errors). The original source for the error might be a
bug - as it seems to be in the problem I'm having.

http://waltritscher.com/blog/ramblings/archive/2005/02/04.aspx

 

[Dino Buljubasic]

Hi Bob,

I have experienced exactly the same problems as you described. Yes,
you are right, it can be quite annoying.

_dino_