When you say, “when debugging a certain thread, visual studio will just jump around randomly to different threads”, do you mean that as you step through code on a particular thread you may hit a breakpoint on a different thread? If so, you can use the Thread window to ‘freeze’ threads other than the one … Read more
this.GetType().Name should work. I think, in your case, you may not have a derived class. If it’s returning the base class name, it shouldn’t have a derived class. Using this on: Base class – Outputs Base class name Derived class – Outputs Derived class name Derived class cast to Base class – Outputs Derived class … Read more
With Visual Studio closed: Delete the solution’s suo file (contains debug information, user settings such as break points, bookmarks, and other user settings.) Delete the Visual Studio cache files (see below) Delete all temporary files (a shift from VS9 to VS10 is that VS10 uses the temp folder) Manually delete all obj and bin folders … Read more
Deleting all of the breakpoints solves the problem when I hit this error. Disabling the breakpoints was not enough – they had to be deleted. I was able to attach to a process numerous times. Once I added a conditional breakpoint (with a few checks), I started getting this error when attempting to attach to … Read more
I had the same problem. I used Microsoft Asp Net WebApi Client 4.0.20710 and it worked for me. Type the following command into Tools > Library Package Manager > Package Manager Console: Install-Package Microsoft.AspNet.WebApi.Client -Version 4.0.20710
With Visual Studio 2013 and .NET 4.5.1, this problem appears to be addressed – and not only in .NET. Further Reading: Debugging Asynchronous Code in Visual Studio 2013 – Call Stack enhancements.
So I resolved my issue. The Diagnostic Tools window currently does not support: Windows Store projects that are using JavaScript Windows Store projects that are running on a Windows Phone Debugging with Use Managed or Native Compatibility Mode In my case I had ‘Use Managed Compatibility Mode’ enabled. To change this go to the following … Read more
In my case this solution is useful: Solution: Disable the “Just My Code” option in the Debugging/General settings. Reference: c-sharpcorner
Right click on the Output window for the Debug selection; here you can select which types of messages to see. The Thread Exit Messages option will be disabled in the example you gave.
I encountered this today. I tried closing the solution but it didn’t work. My mistake I set my solution to Release Mode instead of Debug Mode. I set it to Debug then it worked as expected. I’m using VS 2015 professional.