VS "Cannot set breakpoint breakpoint failed to bind" workaround

Let's start by explaining what I'm experiencing:

Before VS2012 with a good, single-step debugging is not a problem, suddenly there is a situation (for the previous project and the new project is SO): F10 A single-step debugging often run directly to the next breakpoint (very occasionally the situation can be run on a per-process basis); F11 is similar when you run a statement During debugging, you cannot set a breakpoint, and if you set a breakpoint, the prompt appears as shown:

I then searched the internet for "vs can't single-step" information, and made the following attempt:

1. Some people say that there may be computer poisoning, using anti-virus software to kill poison, the problem remains;
2. because I have previously installed VM VMS, so I suspect that there may be a problem with this software, I have the registry to disable vs VMs, not the result, the problem remains;
3. I directly to the VM installation path corresponding to the VS Debug folder deleted, no, the problem remains;
4. simply delete the VM directly, no, the problem remains;
5. try to repair vs with the repair function of the control Panel, the repair process took 40 minutes or so, the problem remains:
6. simply will VS2012 unloading (took 30 minutes or so), re-installed (took more than 20 minutes), not the result, the problem remains;
7. uninstall VS2012, install VS2013, no, the problem is still.

Finally, the "unable to set breakpoint breakpoint failed to bind" message was searched, and a workaround was found at http://94it.net/a/jingxuanboke/2014/1227/434760.html:

Edit and Continue with debug, options, tools, enable native Edit and Continue check-in:

Note: During the debugging process, this option is not changed, as shown, and can be changed by stopping debugging.

VS "Cannot set breakpoint breakpoint failed to bind" workaround