问题
I know Exception Handling is a very important thing and we are doing it in all our projects. The main reason is to log errors that occur at the customers. This works fine and is not problem at all.
But while I am still coding and running the application with Visual Studio I don't want any exception handling at all. I want the debugger stop right at the line the application crashed and not in some error logger I wrote. And I don't want to forward exceptions with throw!
But I am still looking for an easy way to do that. I could write countless #if Debug or #if Release statements all around the try/catch but that is not what I want to do. Is there any other way to deal with this problem?
回答1:
(1) Open Visual Studio with your project
(2) Debug Menu, Exceptions
(3) For the exception types you care about tick the Thrown box.
This will make it so that whenever an exception of the types chosen is thrown you will automatically break into it. When you want to go back to regular debugging go back to that same Exceptions window and click "Reset All" and you'll go back to the default settings.
回答2:
You can configure the Visual Studio debugger to break when the exception is thrown. See the menu Debug -> Exceptions.
For additional information:
How to: Break When an Exception is Thrown
回答3:
in visualstudio Menu Debug->Exception Check all under the column "Thrown". By default, All items will be check for column "User Unhandled"
This way, debugger will break whenever the exception is thrown.
Note: this will not be part of project property
回答4:
Debug > Exceptions (Ctrl+Alt+E), check Thrown on Common Language Runtime Exceptions to throw all exceptions, or select the exceptions you want manually with find all. After you're finished debugging hit Reset All to get back to default.
回答5:
in the VS editor you can set without putting the braekpoints on the type of exceptions the codebreaks - you can set it up using the debug menu -> exception this will allow you to do what you want.
来源：https://stackoverflow.com/questions/2364744/only-break-for-certain-exception-types