Start debugging. During debugging unhandled exception was thrown.
Stop debugging.
Edit code, start debugging with build, and build error appears
I think Visual Studio don't release these files after first debugging.
This error can appear even if exception wasn't thrown, but if debugging was just stopped.
How to fix it?
I think the best and quickest way is to close VS and kill all VS related processes in Task manager.
Try cleaning and then building your project instead of just building your project
Related
When I run a Windows Phone 10 project from Visual Studio 2015 then the following exception pops up after the second run:
Exception thrown at 0x61594533 (WindowsXamlDiagnosticsTap.dll) in remote.exe: 0xC0000005: Access violation reading location 0x00000000.
If there is a handler for this exception, the program may be safely continued.
The exception is raised in debug and release mode. Consecutive runs also fail with this exception. The only fix is to restart Visual Studio after each debug run.
Is there a way to disable this xaml debugging tap? Or what could be the reason for the exception?
Regards,
It might be this known issue: https://github.com/Microsoft/WindowsUIDevLabs/issues/75
Disable Live Visual Tree Debugging as a work around for now.
I recently installed visual studio 2013. In VS2013 i've opened a VS2010 solution.
As i wished to debug the application, i've set some breakpoints on code that are always hit. secondly i've included the option to break on exception (so i know exactly where it went wrong).
yet when i run the application (in Debug)
The exception isn't caught. The exception goes through the normal channels of handling without popping up to me.
None of the breakpoints are hit.
The solution had never such problems in VS2010. Another solution (built & created under VS 2013) doesn't give any problems during debugging. With all the exceptions being thrown and all the breakpoints being hit.
What have i done wrong?
What i've tried sofar:
reinstall VS2013
Changed targeted framework
Clean & rebuild
Attached to process
....
Thank you for your time
I noticed that you attached the process, have you manually detemine the type of code to debug ?
Hello I'm getting this exception thrown at me whenever I try to test a web application via visual studio, any ideas why? I'm building a project using MVC3 model and visual studio 2010
Exception: A first chance exception of type 'StructureMap.StructureMapException' occurred in StructureMap.DLL
First chance exceptions might occur while debugging. They might be handled properly by your code and never propagate when running the application normally but nevertheless Visual Studio shows them in Debug mode. If you don't want to be bothered you could disable them in Visual Studio and they will no longer appear.
I started using Visual Studio 2010 and am missing the dialog box that used pop up in Visual Studio 2008 and earlier that would warn you if there are build errors. The text was something along the line of "There were build errors, would you like to continue using the last successful build?" Then you had the option to continue or cancel (and then go fix the build errors.)
VS2010 is immediately debugging with the last successful build when there are build errors. This is causing frustration for me. How do I turn this warning back on in VS2010? I looked through the options, but didn't see anything that looked like it would work.
This is the setting: Prompt to launch
tools - options - projects and solutions - build and run -"on run, when build or deployment errors occur"
I've worked with VS 2010 Beta 1 for weeks with no issue, but now it crashes on open. I've uninstalled and reinstalled with no success. Does anyone have any advice?
Regards.
Use the JIT debugger to attach a copy of VS2008 to the crashing process and get a stack trace. This may lead you to the problem (which is why I've posted this as an answer). If you still don't know what it is, post the stack trace here and I'll try to let you know what the issue is.
If you don't have symbols available when viewing the stack trace, load symbols from the Microsoft Symbol Server via Tools > Options > Debugging > Symbols. All of the VS2010 runtime modules I've seen have symbols available through there so the traces should be complete.
If you are getting the follow on startup:
"Exception has been thrown by the target of an invocation" on startup
and then it closes, please try the follow :
Open Regedit
Go to "HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\General"
Set the "UILanguage" value to 0x409
it will resolve the startup crash...
Solution if VisualStudio is not installed within the same profile as executed:
Open the commandline in the directory of the datenv executable and try
devenv.exe /resetsettings