I Swear

Jan 25, 2006 visualstudio suggest edit

If Visual Studio .NET 2003 completely crashes during one more debug session in the next hour (I need to be reasonable here), I am going to throw my freaking computer through the window (figuratively speaking).

Thanks for letting me vent.

Found a typo or mistake in the post? suggest edit

Comments

2 responses

Steve Harman • January 25th, 2006
I feel your pain! I am really looking forward to the _upgrades_ that Visual Studio 2005 has to offer in the debugging dept.

Being a JAVA guy by day (read: for my real J-O-B) I am *lucky* to have the Rational Software Development Platform [RAD] (a.k.a.- Eclipse + IBM) at my disposal and it has some SWEET debugging capabilities. My favorite is that while stepping through your code, you can step back to any point in the call stack, essentially going backwards in time. RAD calls this feature "drop to frame," which makes sense as you are really dropping back to a previous frame of reference.

Anyhow, as I said... I hear what you're saying, and here's to hoping that VS 2005 makes debugging a whole lot easier than it is today.

“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug It.” – Brian W. Kernighan
Sean Chase • January 26th, 2006
I hear ya!

http://www.unboxedsolutions.com/sean/archive/2006/01/21/845.aspx