I have been running into a strange Visual Studio (2010) issue when debugging the a solution and I’m hoping someone has some thoughts on how to fix this issue.
At times, during debugging when hitting a break point and start stepping through (F10 or F11) the behavior seen is that of F5 (run), immediately jumping out of the debugger with the page rendered. If a break point is set it’ll run to that but from there it will run to end (or next break point).
The only thing I’ve found to stop this behavior (for a short while) is to close Visual Studio, shutdown IIS, close out IE (yeah, have to do this, seems to hold references) and then go and purge all of the Temporary ASP.NET Files found in all Framework folders (C:\Windows\Microsoft.NET).
This is really making debugging and troubleshooting difficult. Any thoughts on what might be causing this (and how to fix)?
I've had issues with multithreaded debugging in Visual Studio (we use VS 2008 with C# code). Sometimes the debugger would hang, and other times it would just continue the debugging session.
I finally found a workaround for my issues. I selected Visual Studio Tools/Options, Debugging, General, and disabled “Call string conversion function on objects in variables windows (C# and JavaScript only)”.
Internet posts also suggested un-checking “Enable property evaluation and other implicit calls”, but I didn’t need to do that in my case.