page 1 of 1
Comments: 4 | Views: 3879

I have wasted hours trying to work around the bug that sometimes crashes devenv.exe after a command line build (we use devenv as a part of our nightly build process). 

Problems like this make developers (at least this developer) prefer other tools/platforms.

Lot of people have problems with VS.Net crashing: http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=devenv.exe+%22vsw+exception+filter%22.

For your information: the hotfix described in http://support.microsoft.com/default.aspx?scid=kb;en-us;321435 does not work. (And why do I have to call support to get the hotfix? Another time-waster)

JerryP
JerryP
MiniMe
The thinggy with the fixes you have to beg for is easy to explain - they simply did not test them fully.
I got MS to do such fixes and hoped they would get public (in the meantime they are in W2K SP4) but they where private. As developer you are even not allowed to ship the fix with your product.

And now the reason -> you get on a list for that fix, with name, e-mail and phone number - and if any other fix MS does would break your special fix - they call you and warn you. Isn't that great ?
jonathanh
jonathanh
My mod color is red
b_brenna, I've started up a ProductFeedback wiki page just for Visual Studio, and populated it with some of your comments - please expand on them (or delete them, if you don't want them preserved for posterity and/or our devs!) as you see fit.  Read more about it here.
I had the same problem using devenv to build from the command line --> build is successful, then dr w.

I spent a long time tracking it down, and finally isolated it to having an internal class with the same name as an internal class in another assembly.

Renaming or removing this internal class stopped devenv crashing after the build.  The bad design practice here is another issue :I

Hope my find can help others who may have the same issue!

Troy.

page 1 of 1
Comments: 4 | Views: 3879
Microsoft Communities