Edit and continue feature stopped working in Visual Studio 2010

Question

The Visual Studio Edit and Continue feature stopped on Visual Studio 2010, and I don\'t know what has caused the problem.

I am working on a Windows application progr

Answer 1

I tried all the above, none worked. It was apparently due to enabling some low-level debugging options (view registers...)

Tools -> Import and Export Settings -> Reset All Settings

resolved it

Answer 2

I understand this post is old, but I had this issue lately, and this blog post shows me how to fix it.

• Delete the obj folder
• Delete the bin folder. You can copy and paste libraries, data files, etc...back to the folder after removal.
• From VS, menu Solutions -> Clean solution.

This works for me multiple times.

Answer 3

The Edit and Continue feature does not work with the dynamic keyword.

I tried to remove the method that uses a dynamic parameter, and the converted project now works on Visual Studio 2010.

Internet research reveals that is is a bug that has been reported to Microsoft. The link below has more details:

• Dynamic object as method parameters breaks edit and continue for the class and the project

Answer 4

I had used Microsoft's profiler yesterday and afterwards my "Edit and continue" feature got away. I finally realized after hours of frustration that I needed to execute VsPerfCLREnv /globaloff command from command prompt and restart my computer. Now I have my Edit and continue future back. It has nothing to do with target platform by the way. It works with target platform set to Any CPU without any hassle.

Answer 5

I had some Excel file "embed interop types" == true. When I changed it to false, edit and continue started working.

Answer 6

In Visual Studio 2015, I've deleted the .vs folder (where the new style .suo file is), deleted all bin and obj, and also uninstalled Resharper 2015. Edit and Continue is back.

(side note: intellisense is now showing autocomplete almost instantly, whereas it was taking 2 to 5 seconds before, maybe resharper's fault, and maybe unrelated...)