The need for performance hacking for debugging in Visual Studio 2010

Question

I often use Debug -> Exceptions -> check CLR Exceptionsduring debugging sessions. Sometimes an exception throws and handles, but I really want to find the source of the exception. To do this, without seeing the first chance exceptions that don't bother me, I launch my application and then check for CLR exceptions:

, , VS2010 , / reset CLR CTRL + D, E , "" ( , ). , , , , "". , CTRL + D, E.

- ? VS? .

Macro Recorder VS, , , , ?

Answer 1

. .

- .

() ()

,

( ) .