VB Form forgets it is one
From: Jeff Mason (je.mason_at_comcast.net)
Date: 05/27/04
- Next message: Quinn Wilson: "Re: error CS0016: Could not write to output file - build problems - vs.net"
- Previous message: N.Anderson: "RE: Why does my web project load fail to correctly"
- Next in thread: Marc Bernard: "Re: VB Form forgets it is one"
- Reply: Marc Bernard: "Re: VB Form forgets it is one"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 27 May 2004 17:14:37 GMT
I am using VS2003 and have a VB solution with several assemblies. One of them
contains several forms and it seems that randomly, a few of those forms will "forget"
that they are forms and display in the solution view as though they were classes. I
am unable to view them with the form designer, since VS apparently is convinced these
are classes and not forms.
If I inspect the project file "offline", I can see in the <files> section that the
subtype of the offending forms has been mysteriously changed to "Code". If I
manually edit the project file and change this back to "Form" like the others in the
assembly, all appears well, at least for a while until the forms revert back. It
seems that it is always the same few forms that exhibit this behavior. I am unable
to say for certain what I may be doing that causes this - it appears to be random.
I also notice that if I do things like rebuild the solution, exit VS and re-enter and
then rebuild (sometimes more than once) the problem will also go away for a while,
but eventually it will return.
Anybody seen this behavior or have an explanation, and more importantly, a way to
make it stop doing this??
Thanks for any help...
- Next message: Quinn Wilson: "Re: error CS0016: Could not write to output file - build problems - vs.net"
- Previous message: N.Anderson: "RE: Why does my web project load fail to correctly"
- Next in thread: Marc Bernard: "Re: VB Form forgets it is one"
- Reply: Marc Bernard: "Re: VB Form forgets it is one"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|