Visual Studio 2005 Debugging Hell

By | September 3, 2006

I’ve started to continue some C++ programming, well actually tried to continue (but more about that later on). Earlier this year I made the decision to switch from Visual Studio 2003 to 2005. This should have been the right choice as it makes significant improvements in debugging and code editing.

And I must admit on the surface it looks perfect, and during editing I find little problems in creating code. But I am using Visual Assist to improve my programming speed. When I started debugging the hate started. My first attempt resolved in Visual Studio disappearing from the screen and the memory! I couldn’t figure out what happened. The entire Visual Studio shut down, without notice or warning. All I did was hover over a variable to see the value.

Hoping that was the only problem I continued to debug, only finding more problems. And not even in my own code, well not all of them. Some times the debugger just stopped working and the application I was debugging was terminated.

The only good thing in debugging with Visual Studio was when I finally completed my debugging session. No I don’t hate Microsoft, but could they at least release a software package that works!

No I admit I haven’t updated my system in ages, so I checked to see if there were any updates for Visual Studio. Big surprise, there weren’t any! I really hope that I don’t need to do a lot of debugging work in Visual Studio 2005. It’s gonna make me go crazy.

Leave a Reply