Flaky VS.NET Designer
-
Doesn't it irritate you when seemingly innocuous changes to a control or form render the VS.NET designer useless? Change one little thing and you end up with any number of obscure error messages, my personal favorite "An error occured while loading the document. Fix the error, and then load the document again. The error message follows. Unspecified error" I'm actually getting used to not using the forms designer at all because of this. Has anyone experienced something similar? I'm on RC1 Regards Senkwe Just another wannabe code junky
-
Doesn't it irritate you when seemingly innocuous changes to a control or form render the VS.NET designer useless? Change one little thing and you end up with any number of obscure error messages, my personal favorite "An error occured while loading the document. Fix the error, and then load the document again. The error message follows. Unspecified error" I'm actually getting used to not using the forms designer at all because of this. Has anyone experienced something similar? I'm on RC1 Regards Senkwe Just another wannabe code junky
The only time I had the designer do that to me was when something was at fault in my code, especially in the drawing code. If your code throws an uncaught exception this causes the big red x you see in the form. Hopefully this will at least give you some reason as to why you get the designer errors. James Sonork ID: 100.11138 - Hasaki "My words but a whisper -- your deafness a SHOUT. I may make you feel but I can't make you think." - Thick as a Brick, Jethro Tull 1972
-
The only time I had the designer do that to me was when something was at fault in my code, especially in the drawing code. If your code throws an uncaught exception this causes the big red x you see in the form. Hopefully this will at least give you some reason as to why you get the designer errors. James Sonork ID: 100.11138 - Hasaki "My words but a whisper -- your deafness a SHOUT. I may make you feel but I can't make you think." - Thick as a Brick, Jethro Tull 1972
Thanks James, but why then does removing the offending code usually not help? Just another wannabe code junky
-
Thanks James, but why then does removing the offending code usually not help? Just another wannabe code junky
Senkwe Chanda wrote: but why then does removing the offending code usually not help? Off the top of my head it might be pulling a previous version up; I had a very hard time getting VS.NET to sync the latest build of the control and my test projects. What I wound up doing was having 2 VS.NETs open, one to work on my control the other to do testing with; before I would compile the control I would remove the reference to it from the project; recompile the control then re-add the reference. This was before I found out about project references though, and now I don't have VS.NET installed so I can't see if that solves the problems I was experiencing. HTH, James Sonork ID: 100.11138 - Hasaki "My words but a whisper -- your deafness a SHOUT. I may make you feel but I can't make you think." - Thick as a Brick, Jethro Tull 1972
-
Senkwe Chanda wrote: but why then does removing the offending code usually not help? Off the top of my head it might be pulling a previous version up; I had a very hard time getting VS.NET to sync the latest build of the control and my test projects. What I wound up doing was having 2 VS.NETs open, one to work on my control the other to do testing with; before I would compile the control I would remove the reference to it from the project; recompile the control then re-add the reference. This was before I found out about project references though, and now I don't have VS.NET installed so I can't see if that solves the problems I was experiencing. HTH, James Sonork ID: 100.11138 - Hasaki "My words but a whisper -- your deafness a SHOUT. I may make you feel but I can't make you think." - Thick as a Brick, Jethro Tull 1972
I had a terrible time getting my control icons to work. I finally discovered that VS.NET was caching the icons based on the assembly version. I had no AssemblyInfo.cs file (or its equivalent) and so my version stayed at 0.0.0.0 and my icon was not changing. Once I set my version to 1.0.0.* my icons worked properly. Otherwise I have no problem using controls from one project in another project under the same solution and under the same instance of the IDE. I just have to remember to build my control assembly before trying to use it (ie in the Form Designer of another project). -- Peter Stephens