I manually migrated a Visual Studio 2012 "website" to a "ASP web project" to be able to use environment-specific web.configs (using transformation).
After migration my debugger does not stop anymore at exceptions.
In my output view I can see that a NullReferenceException is raised, my HTTP-REST-client receives "400 bad request", but the debugger ignores that exception.
I followed the instructions to enable exceptions ( How do I allow breaking on 'System.NullReferenceException' in VS2010? ). In the dialog "debugging"=>"Exceptions..." NullReferenceExceptions are enabled and resetting all checkboxes does also not help.
Breakpoints are working as expected.
The compiler also has some strange behaviour: compilation will succeed even if the code contains syntax problems. (But this might be a separate issue)
How can I reenable the debugger?
The issue seems to be fixed after I enabled "Just My Code" in "Options"=>"Debugging"=>"General". (see also Visual Studio 2013 "break on handled exceptions" not working, not breaking ).
Is "Just my code" enabled? You should try to set it as enable and see if it works.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With