PC Review
Forums
Newsgroups
Microsoft DotNet
Microsoft Dot NET Framework Forms
Controls disapearing after compiling
Forums
Newsgroups
Microsoft DotNet
Microsoft Dot NET Framework Forms
Controls disapearing after compiling
![]() |
Controls disapearing after compiling |
|
|
Thread Tools | Rate Thread |
|
|
#1 |
|
Guest
Posts: n/a
|
Hi,
I'm having a very strange bug. It seems that after I compile a Release version of my code, the user-controls that I'm using (created by me.. different project, same solution, compiled first) disapear! When I load a form they are all missing the controls and I get tons of errors. If I don't open the form (in design mode) and try to run it, it runs fine, but once I open it, if I save the form, I'm screwed! Has anyone experienced this problem? is there a way around it? Thanks in advance, Philip Tepedino Siemens Westinghouse Generation Services ftepedino@swgs.net |
|
|
|
#2 |
|
Guest
Posts: n/a
|
I have experienced this. Very annoying!
if you are modifying a user control, make sure that any form that has that control on it is closed within visual studio. I think what happens is if you modify the control, attempt to compile, and if there is a bug/error, any form that has that control on it gets screwed up. It actually removes all of the code from InitializeComponent. I don't know why it does this, but I got into the habbit of closing all the forms from design view whenever I modify my user controls. HTH "Philip Tepedino" <ftepedino@swgs.net> wrote in message news:O76C62yvDHA.2444@TK2MSFTNGP12.phx.gbl... > Hi, > > I'm having a very strange bug. > It seems that after I compile a Release version of my code, the > user-controls that I'm using (created by me.. different project, same > solution, compiled first) disapear! > When I load a form they are all missing the controls and I get tons of > errors. If I don't open the form (in design mode) and try to run it, it runs > fine, but once I open it, if I save the form, I'm screwed! > > Has anyone experienced this problem? is there a way around it? > > Thanks in advance, > > Philip Tepedino > Siemens Westinghouse Generation Services > ftepedino@swgs.net > > |
|
|
|
#3 |
|
Guest
Posts: n/a
|
I'll give that a try.
I wish MS had some info on this and some kind of way around it! Thanks for the help, Philip "TheGrudge" <anonymous@discussions.msdn.com> wrote in message news:OWeC$CGxDHA.2408@tk2msftngp13.phx.gbl... > I have experienced this. Very annoying! > > if you are modifying a user control, make sure that any form that has that > control on it is closed within visual studio. I think what happens is if you > modify the control, attempt to compile, and if there is a bug/error, any > form that has that control on it gets screwed up. It actually removes all of > the code from InitializeComponent. I don't know why it does this, but I got > into the habbit of closing all the forms from design view whenever I modify > my user controls. > > HTH > > "Philip Tepedino" <ftepedino@swgs.net> wrote in message > news:O76C62yvDHA.2444@TK2MSFTNGP12.phx.gbl... > > Hi, > > > > I'm having a very strange bug. > > It seems that after I compile a Release version of my code, the > > user-controls that I'm using (created by me.. different project, same > > solution, compiled first) disapear! > > When I load a form they are all missing the controls and I get tons of > > errors. If I don't open the form (in design mode) and try to run it, it > runs > > fine, but once I open it, if I save the form, I'm screwed! > > > > Has anyone experienced this problem? is there a way around it? > > > > Thanks in advance, > > > > Philip Tepedino > > Siemens Westinghouse Generation Services > > ftepedino@swgs.net > > > > > > |
|
![]() |
|
| Thread Tools | |
| Rate This Thread | |
|
|

Main Page 

