"My apps are fairly complex" feedback

Amit criticizes my approach from here, which is actually an echo from Cyrus's post about no using of debug in managed code.

"Exceptions are very expensive (as discussed here) and should be used wisely!"

Totally agree with that. My point though was that during testing one can find out easily (imho) where the bug is by looking through exception stack trace.

"Sure there are applications that would not warrant the use of a debugger (like HelloWolrd *grin*), but most of the applications I design and work on are fairly complex and the debugger is a very invaluable tool!"

BTW, I'm not a "sample apps" or "HelloWorld" programmer. The applications that I deal with are large scale .NET applications, all of them developed from scratch and all of them in the production environment. They are multilayered and provide WS-API in variations. Nevertheless the code there is generic and rather simple and is easy to maintain. If you think that debugger is invaluable during your work on your code I can ask you what will happen to the programmer that would have to maintain your stuff some day ?

Related Posts:

• Use Debugger in Visual Studio .NET ?
• Google: High resolution version
• Day X
• Google Active Directory June
• New DataSource... issue and... WYSIWIG ?
• Cancel feature request
• Why C# is Less Visible on Web than Java
• Feature request for Whidbey
• Email worm flood waves
• Accessing the internet - offline

I agree to some extent that by just looking at the stack trace you can find out the bugs - but those are the simpler ones. For the more complex ones where the appplication does not crash with your results are different (could be because of invalid data or screwed up logic) the deubbger is a must.

Also, when I posted I was not pointing to you as the Hello World prgrammer, it was a joke trying to make a point. I apologize if that is how it was protrayed.

Amit, it's ok, I didn't took it that personally. Thanks for your feedback. :)