"The breakpoint is not currently being killed. Solution for problem with source code different from original version "
Source: Internet
Author: User
When you debug a program in VS, you occasionally encounter a breakpoint that you cannot enter, and at the breakpoint you set it, you will be prompted "... The breakpoint is currently not being killed. The source code differs from the original version ... "Information. 1 Clean up the solution, and then rebuild Solution 2 Remove all Debug directory 3 Close solution, delete ncb, suo file, delete debug directory and so on, re-generate the above methods can not solve the problem persists;
After groping and analysis, found that as long as in the module can not enter the breakpoint, casually enter something, let the module appear unsaved flag, and then recompile. (Strangely, I have deleted the entire directory, it should be recompiled, why it has to have an edit tag.) For the time being unclear why)
Record it and hope to be helpful to a friend who has encountered the problem.
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.
