I keep getting this error below every so often with Visual Studio 2013. I believe it has to do with the async nature of connecting it with the browser. Is there a reason why this is happening, a bug?
An exception of type 'System.Threading.ThreadAbortException' occurred in mscorlib.dll
and wasn't handled before a managed/native boundary
Open the debug options (menu bar -> Debug -> Options) and disable:
"Break when exceptions cross AppDomain or managed/native boundaries (Managed only)"
"Enable Just My Code"
(Under Debugging \ General)
Msdn: source
Related
While doing pair-programming on an React project with Visual Studio Professional 2017, my partner was working on my machine and disabled some debugger option to see less warnings. I want to undo what he did, but he is not available any more, so that's why I am asking here. I remember faintly that he said something about disabling "some breaking".
I am sure it must be somewhere in the options window which appears after Debug > Options and on that popup somewhere under the entry Debugging. I attached a screenshot of Debugging > General. I already tried the toggling the 3rd check-box, but that did not do the trick.
The interesting thing is that in the sub-window Output I used to see all those exceptions logged, but I do not see them anymore.
References
How to turn off warnings while debugging in VS Code?
Enable a single warning in Visual Studio
How to re-enable breaking on unhandled exception in Visual Studio 2012 Express for Web?
RavenDB throws tons of handled and expected exceptions internally. I have Enable Just My Code checked. I've tried clearing my symbol cache, but if I have Debug > Exceptions > Common Language Runtime Exceptions > Thrown checked, Visual Studio still breaks on these internal RavenDB exceptions.
Why does Visual Studio think RavenDB qualifies as "Just My Code"?
I'm using Web Api and when an exception happens in my code (for example a bad cast), and the debugger is attached, the exception is not thrown in Visual Studio. I just get the 500 internal server error on the browser side with the exception details but it's a pain because I have to track down what line it's thrown on.
I don't believe this was always the case, and thought it must be one of my settings messed up but I have already tried to reset visual studio settings to no avail.
How can I get the debugger to break again on 500 internal server errors.. I don't want to enable first chance exceptions.
Tools -> Options -> Debugging -> General, Ensure that "Enable Just My Code" is checked.
In visual studio Debug->Exceptions for exceptions that you need or for all of them select checkbox in the Throw column. It's because by default Asp.Net runtime handles all exceptions. MSDN
I'm debugging a web site (not web project, unfortunately) in Visual Studio 2012 with Internet Explorer 9 and it seems to keep breaking on JavaScript exceptions with the standard Unhandled exception at line x, column y in script block dialog. This happens in a new tab titled script block [dynamic].
At this stage I'm really not concerned with the underlying exception, I just don't want Visual Studio to tell me about the exceptions at all.
I've changed every obvious setting I can think of. So:
Visual Studio Settings
Exception settings -> JavaScript Runtime Exceptions: both Thrown and User-unhandled are unchecked.
Tools -> Options -> Debugging -> Just-In-Time: Script is unchecked
Internet Explorer 9 Settings
Internet Options -> Advanced: Disable Script Debugging (Internet Explorer) and Disable Script Debugging (Other) are both unchecked.
This doesn't happen if I debug using Firefox or Chrome, but unfortunately I'm forced to use Internet Explorer 9.
How can I fix this problem? Are there any options I might be missing?
Try the Web Essentials extension for VS. I'm fairly sure it stopped when i installed this. alternatively you can try Debug=>Attach to=> then Select.... (but you might have to do this a lot...)
As far as I remember, Visual Studio (both 2008 and 2010) used to have an option to break either on thrown exceptions or on unhandled exceptions. Now when I bring up the Exceptions dialog (Ctr+Alt+E), it just offers to break when an exception is thrown:
I've tried resizing to the columns in that dialog, but that did not help. Is this a bug, or am I missing something?
This seems to indicate it can occur if you don't have "Enable Just My Code (Managed Only)" enabled.
Edit: just tried it here (VS 2008) and I can verify that disabling that option will cause the User-Unhandled column to disappear. You can find the option here: Tools -> Options -> Debugging -> General
I have this as well when I've enabled source-server support in VS.NET.
When I have source-server support disabled, then the option to break on unhandled exceptions is still visible.
But, a thought: is it necessary to be able to specify that the IDE should break when an exception is unhandled ? As far as i know, this is just default behaviour, isn't it ? So, what's the use to be able to specify that option ?