Use Debugger in Visual Studio .NET ?

Cyrus says he does not have to use debugger in managed code.

"With managed code I tend to write smaller, simpler objects with simple messages that are easy to understand and verify. Tracking a bug down is usually quite simple because you'll either have an exception, or you can pretty easily figure out where the error occurred."

Totally agree. I program in C#. I remember used debugging feature in Visual Studio only twice from march 2002 - just to show folks how to attach the studio to the ASPNET process. There is just no need for debugger, IMHO. If compiler does not find the error - you would get runtime exception. And you have trace in web also. More than that. It is quite a lot time for now that I compile all my projects in release mode.

Related Posts:

• 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
• Target line

Hi,
I don't think I agree with that viewpoint. Exceptions are very expensive and one needs to be careful on how you are using it. I have found the debugger invaluable - especially with the large complex applications I work on. Now sure how you attribute this statement.

Regards,
Amit.

Amit: "Exceptions are very expensive and one needs to be careful on how you are using it."

Agree. But I don't rely on exceptions. My point was that one can find out where the bug is from the stack trace.
Exceptions in .NET is a big topic itself.