There is a known bug in Visual Studio that prevents you from using the form constructor in a subclass of an abstract form.
This problem has already been clarified and solved most elegantly by the City Potato ; this is not the part that I'm having problems with. The trouble is that I duplicated the technique described by Urban Potato and included it in my project (which can be quite large), and now every time I try to open the constructor of my derived form, I get that Microsoft is "terribly sorry, old guy, but I have to kill you now "(reminiscent of" Otto in Fish Waid Wanda "), which says:" Microsoft Visual Studio 2005 has encountered a problem and needs to close. We are sorry for the inconvenience. "
But here is the real kicker: if you just ignore this message and take it to the lower right corner of the screen, you can continue to work, completely normal! Just do not click the "Send Error Report" or "Do Not Send" buttons, then VS does .
However, this phenomenon is very annoying, and I would love to work without feeling that my IDE is just looking for some really nasty way to get back to me to leave now - or otherwise.
Additional useful information: the same behavior can be duplicated on all other computers in my office; this is nothing special for my car. Obviously, something in the project / code violates the IDE, but at least I know that the design template works, because after I ignore the alarm message, the designer works fine. I just don’t know where to start looking for what causes this problem.
Any ideas?
Thanks!
source share