By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,453 Members | 3,194 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,453 IT Pros & Developers. It's quick & easy.

Can't get design view for form?

P: n/a
I have a form with a Form1_Load() Subprocedure and no other code. For some
reason, the design view does not come up. If I add a new form, the design
view does come up. The form does appear when I execute the EXE. The design
view for this form use to come up but I'm not sure when it stopped
appearing.

I do notice the form1.vb and class1.vb files in the Solution Explorer
(Visual Studio.NET) have little arrows in the bottom left corner of their
icons. What are these?

Previously, I did move the vb files to another folder and then the project
file. Could this have affected the form? Any other suggestions?

Thanks,
Brett
Nov 21 '05 #1
Share this Question
Share on Google+
8 Replies


P: n/a
Yes, if you now click on the design view and it shows a big red X? Then you
moved some code to a place it doesnt like.

A nice improvement would be if the fantastic .net IDE would complain in the
code view about this.

Ive found this happens when I simply add another namespace and reference
existing code, design view says NO.

One of the habits Ive found works great is to do a daily freeze of the
project, sometimes a couple of times per day, where you save the entire
solution in some name with that days date, then continue on with the
original name. So you can always back up without losing more than about 1
days work.

I cant recall exactly what makes design view get upset, but yes, moving
files and folders will cause this. See if you can back up to where it was

"Brett" <no@spam.com> wrote in message
news:O8**************@tk2msftngp13.phx.gbl...
I have a form with a Form1_Load() Subprocedure and no other code. For some reason, the design view does not come up. If I add a new form, the design
view does come up. The form does appear when I execute the EXE. The design view for this form use to come up but I'm not sure when it stopped
appearing.

I do notice the form1.vb and class1.vb files in the Solution Explorer
(Visual Studio.NET) have little arrows in the bottom left corner of their
icons. What are these?

Previously, I did move the vb files to another folder and then the project
file. Could this have affected the form? Any other suggestions?

Thanks,
Brett

Nov 21 '05 #2

P: n/a
Did you try rebuilding the project. I run into this problem
occasionally. Or try the toolbar-view-designer button.

Nov 21 '05 #3

P: n/a
Yes - but that didn't do anything.
"PAPutzback" <Ph**************@insightbb.com> wrote in message
news:ut**************@TK2MSFTNGP10.phx.gbl...
Did you try rebuilding the project. I run into this problem occasionally.
Or try the toolbar-view-designer button.

Nov 21 '05 #4

P: n/a
The periodic saving with dates is a good idea. Since this is a new project
is just added a new form and deleted the old.

Brett

"Bradley1234" <so*****@yahoo.com> wrote in message
news:baYAd.12310$tG3.9580@trnddc02...
Yes, if you now click on the design view and it shows a big red X? Then
you
moved some code to a place it doesnt like.

A nice improvement would be if the fantastic .net IDE would complain in
the
code view about this.

Ive found this happens when I simply add another namespace and reference
existing code, design view says NO.

One of the habits Ive found works great is to do a daily freeze of the
project, sometimes a couple of times per day, where you save the entire
solution in some name with that days date, then continue on with the
original name. So you can always back up without losing more than about 1
days work.

I cant recall exactly what makes design view get upset, but yes, moving
files and folders will cause this. See if you can back up to where it was

"Brett" <no@spam.com> wrote in message
news:O8**************@tk2msftngp13.phx.gbl...
I have a form with a Form1_Load() Subprocedure and no other code. For

some
reason, the design view does not come up. If I add a new form, the
design
view does come up. The form does appear when I execute the EXE. The

design
view for this form use to come up but I'm not sure when it stopped
appearing.

I do notice the form1.vb and class1.vb files in the Solution Explorer
(Visual Studio.NET) have little arrows in the bottom left corner of their
icons. What are these?

Previously, I did move the vb files to another folder and then the
project
file. Could this have affected the form? Any other suggestions?

Thanks,
Brett


Nov 21 '05 #5

P: n/a
Brett wrote:
Yes - but that didn't do anything.
"PAPutzback" <Ph**************@insightbb.com> wrote in message
news:ut**************@TK2MSFTNGP10.phx.gbl...
Did you try rebuilding the project. I run into this problem occasionally.
Or try the toolbar-view-designer button.


Did you lose the code from this
#Region " Windows Form Designer generated code "

All the code needed to create the form should be in there. If you run
the project does the form show?
Nov 21 '05 #6

P: n/a
post your code for the form?

Try remming out the code inside the intializecomponents (sp?) function.
Then bring back a section at a time. That should narrow it down to what
part of your code that is causing the issue.

Chris

"Brett" <no@spam.com> wrote in message
news:O8**************@tk2msftngp13.phx.gbl...
I have a form with a Form1_Load() Subprocedure and no other code. For some
reason, the design view does not come up. If I add a new form, the design
view does come up. The form does appear when I execute the EXE. The design
view for this form use to come up but I'm not sure when it stopped
appearing.

I do notice the form1.vb and class1.vb files in the Solution Explorer
(Visual Studio.NET) have little arrows in the bottom left corner of their
icons. What are these?

Previously, I did move the vb files to another folder and then the project
file. Could this have affected the form? Any other suggestions?

Thanks,
Brett

Nov 21 '05 #7

P: n/a

"PAPutzback" <Ph**************@insightbb.com> wrote in message
news:e4**************@TK2MSFTNGP11.phx.gbl...
Brett wrote:
Yes - but that didn't do anything.
"PAPutzback" <Ph**************@insightbb.com> wrote in message
news:ut**************@TK2MSFTNGP10.phx.gbl...
Did you try rebuilding the project. I run into this problem occasionally.
Or try the toolbar-view-designer button.


Did you lose the code from this
#Region " Windows Form Designer generated code "

All the code needed to create the form should be in there. If you run the
project does the form show?


Yes - the form shows. I only had a small bit of code. I just copied it
from the old form into the new one. There weren't any design features so
nothing to worry about there. This probably wouldn't work with a more
complicated form.
Nov 21 '05 #8

P: n/a
Ok, Thanks. I've already deleted the form and added a new. Will try your
suggestion next time.

Brett

"Chris, Master of All Things Insignificant" <chris@No_Spam_Please.com> wrote
in message news:%2****************@TK2MSFTNGP12.phx.gbl...
post your code for the form?

Try remming out the code inside the intializecomponents (sp?) function.
Then bring back a section at a time. That should narrow it down to what
part of your code that is causing the issue.

Chris

"Brett" <no@spam.com> wrote in message
news:O8**************@tk2msftngp13.phx.gbl...
I have a form with a Form1_Load() Subprocedure and no other code. For
some reason, the design view does not come up. If I add a new form, the
design view does come up. The form does appear when I execute the EXE.
The design view for this form use to come up but I'm not sure when it
stopped appearing.

I do notice the form1.vb and class1.vb files in the Solution Explorer
(Visual Studio.NET) have little arrows in the bottom left corner of their
icons. What are these?

Previously, I did move the vb files to another folder and then the
project file. Could this have affected the form? Any other suggestions?

Thanks,
Brett


Nov 21 '05 #9

This discussion thread is closed

Replies have been disabled for this discussion.