Shows the Ctrl+Alt+E exception dialog instantly
On my laptop/sln Showing the Ctrl+Alt+E exception dialog takes around 6s in VS2010, 4s in VS2008 and 2s in dev11DeveloperPreview (even faster would be great).
When an exception pops when debugging, provides a quick an easy way to stop monitoring the exception type for future exception raised. Opening the exception type management dialog each time is a pain + this dialog is so slow to open (4 seconds!).
This suggestion is now complete with Visual Studio 2015 CTP 6: http://blogs.msdn.com/b/visualstudio/archive/2015/02/23/visual-studio-2015-ctp-6-and-team-foundation-server-2015-ctp-released.aspx
For more information, please, read: http://blogs.msdn.com/b/visualstudioalm/archive/2015/02/23/the-new-exception-settings-window-in-visual-studio-2015.aspx
If you would like to follow news about the Visual Studio Debugger, please subscribe to our blog or to our twitter account.
Thanks for sharing this suggestion with us and for using Visual Studio!
Visual Studio Diagnostics
Moved this to the Debugger path
Maria Ghiondea - MSFT commented
The second part of this item has been fixed - https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2221976-fast-disable-button-for-exceptions
Also, make a button 'disable catching this exception type' when an exception pops at debug-time, which will discard the need to show the Exception dialog often.
Andrew Skalkin commented
Can anyone tell me if they implemented this feature in VS2012?
I want to ignore exceptions in logger config style (with wildchars):
Allon Guralnek commented
Even better, make it a dockable window. And allow me to have a "Favorites" tab where only the exceptions I care about are visible, so I don't have to "Find" exceptions. In addition the "Favorites", a "Recent" tab of recently thrown exceptions (what appears in the Output windows) would also be nice to quickly break on some new suspicious exception.
It would also be nice to have an option to have finer grained control so that it would be possible to ignore an exception at a specific location (user code, specific function, specific DLL) as some generic exceptions like null pointers might get thrown at many locations but a few should be ignored.
Also a way to temporarily enable or disabled all exceptions (or load/save exceptions settings) would be nice.
An option to ignore the exception for this debugging session would also be nice.
Debugging attributes might also be useful so that once could mark code at function or class level with something like [DebuggerStopOnException(false)] and it should apply by default to any function called by the function on whioch the attribute was added.
Andrew Skalkin commented
The absence of that feature, combined with the fact that .NET throws and handles exception in non-exceptional situations (such as FileNotFound when the corresponding *.XmlSerializers.dll assembly has not been pre-built), drives me nuts for the past 10 years. I am aware that I can set it up to break on my code only, but that doesn't help much. I would also suggest to make exception management more powerful, such as adding the ability to suppress a particular exception on a particular stack trace, etc.
YES PLEASE! Put a checkbox on the exception dialog that disabled "break on thrown" for the current exception.
+1 For the idea of making a button to disable stopping the debugger on specific exceptions when that exception happens.
This would save me a whole lot of annoying SocketExceptions from background threads while debugging.
Richard Beier commented
Great idea. This would help me get past Unity's frequent SynchronizationLockExceptions...