Note that there are some explanatory texts on larger screens.

plurals
  1. POToggle "Break when an exception is thrown." using macro or keyboard shortcut
    text
    copied!<blockquote> <p>Edit: Visual Studio 2015's new exception window is so much faster than the old dialog that I no longer care as much about using a keyboard shortcut for it.</p> </blockquote> <p>Is there a macro or keyboard shortcut that will toggle "break when an exception is thrown" without using the GUI?</p> <p>Opening the dialog with ctrl+alt+e and checking the "Common Language Runtime Exceptions" "Thrown" box then clicking OK is simple enough, but this is something I do a lot. I would rather have a keyboard shortcut for this.</p> <p>This question is a duplicate of <a href="https://stackoverflow.com/questions/323390/any-have-a-visual-studio-shortcut-macro-for-toggling-break-on-handled-unhandled-e">Any have a Visual Studio shortcut/macro for toggling break on handled/unhandled exceptions?</a></p> <p>However, the poster accepted an answer that doesn't really work, and I would really like an answer that <strong>does</strong> work.</p> <p>The answer in the duplicate question is not acceptable because it toggles only one specific exception, not the entire CLR group.</p> <p>"Well write a loop then." you say. But not so fast! <a href="http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/b0efc1fd-879e-4882-8992-c0ecd4cd980f" rel="nofollow noreferrer">Someone tried that already</a> and it was uselessly slow. (Yes I've verified that its slow on my system as well.)</p> <p>So the challenge is to use a macro to toggle the entire CLR Exceptions category in less than 1 or 2 seconds. This question is a duplicate of <a href="https://stackoverflow.com/questions/323390/any-have-a-visual-studio-shortcut-macro-for-toggling-break-on-handled-unhandled-e">Any have a Visual Studio shortcut/macro for toggling break on handled/unhandled exceptions?</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload