Julia Lerman Blog

INETA Poster Child blabbing about community and code

Sponsors

.About Me

.Chick Blogs (yes I am highlighting them!)

.Coming Soon

.NET User Groups

A small slice of blogs I read

Articles & Talks

Conferences

Developer Book Reviews

Elsewhere...

Showing Off

some random U.G. Leader Blogs

Tablet

The Disappearing Form Designer

Every once in a while, while working on a windows app in VS.NET2003, I lose the design view of a particular form. The solution Explorer only displays it as a class and there is no way to access the design view of the form. The components all still exist in the code. It's a little bit of a heart stopper. But then removing and then readding the project from the solution brings back the form. 'Sup with that?

[syndicated from Julia Lerman's Don't Be Iffy Blog. Please refer and comment here]

Posted: Jan 15 2004, 09:59 AM by jlerman | with 6 comment(s)
Filed under:

Comments

mp said:

I have found that the form designer gets confused when other classes are placed before the Form class in the .cs file.

I have actually stopped defining new classes inside of any form files. My problems have gone away.

Don't know if this is the same issue for you.
# January 15, 2004 11:26 AM

julie lerman said:

I know this is an issue with web services (not an issue, just a rule). In the case of my form, however, there is no class prior to the form itself. Good idea to check that though.
# January 15, 2004 11:36 AM

Rick Strahl said:

Julia, I see this all the time and from my experience it's caused by the form designer not properly finding the InitializeComponent block it needs to render the form. The solution in almost all (but not ALL) cases is to put the Form Designer Generated code at the very top of the class, or at least before any other methods. Works for me...
There are a also some third party components that can screw with things. I've had issues with ActiveReports and according to their support it's due to their .licx file having spaces in it. Remove the spaces and the Form Designer and code editors are happy.
# January 16, 2004 3:55 PM

julie lerman said:

such a smart boy. Thanks Rick.
# January 16, 2004 4:11 PM

Tom Faller said:

For unknown reasons it seams that sometimes controls are placed outside the Form Designer Reagion by the Form Designer itself. Cutting and pasting these control declarations inside the region makes it work again.
# February 17, 2004 4:13 AM

Julie Lerman said:

interesting - I'll take a look for that ...thanks
# February 17, 2004 8:12 AM
Leave a Comment

(required) 

(required) 

(optional)

(required)