blocks|key|5235257|text|正如它所说的，“源代码与原始版本不同”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5235258|右键单击解决方案资源管理器中的项目文件夹，然后选择Clean。构建项目的新版本，断点将再次工作！|offset|length|style|CODE|5235259|entityMap^0|0|P|5|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

As it says, the "source code is different from the original version".

Right click on the project folder inside the solution explorer and choose to <code>Clean</code>. Build a new version of the project and the breakpoint will work again!

blocks|key|1476542|text|如果在Debug+build+configuration中取消选中DLL项目，您的新代码将永远不会生成！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1476543|转到Build+-->+Configuration+Manager+...+(在VS2010中)并检查包含您试图调试的代码的项目是否针对当前构建配置进行了检查。|offset|length|style|CODE|1476544|entityMap^0|0|2|Z|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

If you have unchecked the DLL project in the Debug build configuration, your new code will never be built!

Go to <code>Build --&gt; Configuration Manager ...</code> (in VS2010) and check if the project with the code you're trying to debug is checked for the current build configuration.

blocks|key|1708396|text|对我来说，这是在WebSite项目中工作的时候。清理完这些临时文件夹后，我得到了正确的编译器错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1708397|1708398|C:\Documents+and+Settings\%25username%25\AppData\Local\Temp\Temporary+ASP.NET+Files|unordered-list-item|offset|length|style|CODE|1708399|C:\windows\Microsoft.NET\Framework\v4.0.30319\Temporary+ASP.NET+Files|1708400|1708401|当我发现一个我故意移到子文件夹中的类文件以某种方式重新出现在根文件夹中时，我终于解决了这个问题。当我在编辑另一个的时候，VS正在使用那个。|1708402|entityMap^0|0|0|0|27|0|0|1X|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|S|8|@$F|T|G|U|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|V|8|@$F|W|G|X|H|I]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|P|$]]

For me it was while working on a WebSite project. After cleaning up these temp folders I got the proper compiler errors back:

<ul>
<li><code>C:\Documents and Settings\%username%\AppData\Local\Temp\Temporary
ASP.NET Files</code></li>
<li><code>C:\windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET
Files</code></li>
</ul>

I finally resolved the problem when I discovered that a class file I had intentionally moved into a subfolder, somehow reappeared in the root folder. VS was using that one while I was editing the other.

blocks|key|1708115|text|你做过这个吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1708116|Would+you+like+to+continue+and+run+the+last+successful+build?|offset|length|1708117|如果您勾选了该框并按下了"Yes“，即使您的项目没有编译，您也会运行上一次成功的构建。这意味着，无论何时设置断点，都会收到该错误。|1708118|尝试更改此值：|1708119|1708120|Tools+|unordered-list-item|1708121|Options+|1708122|项目和解决方案|1708123|生成并运行|1708124|运行时，发生生成或部署错误:+Do+not+Launch|1708125|1708126|1708127|1708128|1708129|1708130|​|1708131|1708132|1708133|1708134|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/596142/would-you-like-to-continue-and-run-the-last-successful-build^0|0|0|1P|0|0|0|0|0|1|2|3|4|4|3|2|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1E|8|@]|9|@$D|1F|E|1G|1|1H]]|A|$]]|$1|F|3|G|5|6|7|1I|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1J|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|1L|8|@]|9|@]|A|$]]|$1|N|3|O|5|M|7|1M|8|@]|9|@]|A|$]]|$1|P|3|Q|5|M|7|1N|8|@]|9|@]|A|$]]|$1|R|3|S|5|M|7|1O|8|@]|9|@]|A|$]]|$1|T|3|U|5|M|7|1P|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1V|8|@]|9|@]|A|$]]|$1|12|3|11|5|6|7|1W|8|@]|9|@]|A|$]]|$1|13|3|11|5|6|7|1X|8|@]|9|@]|A|$]]|$1|14|3|11|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]]|16|$17|$5|18|19|1A|A|$1B|1C]]]]

Did you ever do this?

<a href="https://stackoverflow.com/questions/596142/would-you-like-to-continue-and-run-the-last-successful-build">Would you like to continue and run the last successful build?</a>

If you ticked the box and pressed "Yes" you will get the last successful build running even though your project does not compile. This means that whenever you set a breakpoint, you will get that error.

Try changing this value:

<ul>
<li>Tools

<ul>
<li>Options

<ul>
<li>Projects and Solutions

<ul>
<li>Build and Run

<ul>
<li>On Run, when build or deployment errors occur: Do not Launch</li>
</ul></li>
</ul></li>
</ul></li>
</ul></li>
</ul>

blocks|key|1708363|text|去|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1708364|1708365|工具|unordered-list-item|1708366|选项|1708367|调试|1708368|General|1708369|1708370|1708371|1708372|1708373|​|1708374|1708375|1708376|取消选中要求源文件与原始版本完全匹配|1708377|entityMap^0|0|0|1|2|3|3|2|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Z|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|12|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|17|8|@]|9|@]|A|$]]|$1|R|3|Q|5|6|7|18|8|@]|9|@]|A|$]]|$1|S|3|Q|5|6|7|19|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1A|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|W|$]]

Go to

<ul>
<li>Tools
<ul>
<li>Options
<ul>
<li>Debugging
<ul>
<li>General</li>
</ul></li>
</ul></li>
</ul></li>
</ul>

Uncheck Require source files to exactly match the original version

blocks|key|1476618|text|在Solution+Configurations中选择Debug，而不是Release|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1476619|​|1476620|📷|atomic|1476621|1476622|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/0179ed2b9a1c9d74584346b92d13e058.jpeg|imageAlt^0|1|N|R|5|10|7|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|K|3|G|5|6|7|16|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S|T|-4]]]]

Select Debug in Solution Configurations, instead of Release

<img src="https://i.stack.imgur.com/5Sa3m.jpg" alt="screenshot of menu">

blocks|key|3818612|text|注意VS中的"Output“窗口。它将告诉您加载了哪些程序集以及加载的时间。您可能会看到正在加载文件夹中某个较旧版本的程序集。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3818613|例如，如果您有多个程序集，并且当前正在尝试中断其中一个支持程序集，则CLR将处理程序集解析，这可能会加载另一个程序集文件，而不是您在项目中引用的文件。|3818614|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Pay attention to the "Output" window in VS. It will tell you what assemblies are loaded and when. You may see that an older version of your assembly somewhere in the folder is being loaded. 

For example if you have multiple assemblies and you are currently trying to break in one of the support assemblies, the CLR will handle the assembly resolving, which may load another assembly file than the one you have referenced in the project.

blocks|key|3819017|text|关闭Visual+Studio并重新打开解决方案可以解决这个问题，也就是说，这是集成开发环境本身的一个错误(我正在运行VS2010)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3819018|如果有多个Visual+Studio实例正在运行，则只需关闭运行出现问题的解决方案的实例。|3819019|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Closing Visual Studio and reopening the solution can fix the problem, i.e. it's a bug within the IDE itself (I'm running VS2010).

If you have more than one instances of Visual Studio running, you only need to close the instance running the solution with the problem.

blocks|key|3819792|text|从Visual+Studio+2017+15.3.1到15.3.5，出现了解决此问题的新方法。如果您使用的是EditorConfig，则charset=utf8选项会导致这些症状。VS团队已经复制了这个和says+they+are+working+on+it。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3819793|因此，一种解决方法是注释掉.editorconfig文件中的charset=utf8行。|3819794|编辑:这个问题应该从VS15.5开始修复。|3819795|entityMap|0|LINK|mutability|MUTABLE|url|http://editorconfig.org/|1|https://developercommunity.visualstudio.com/content/problem/100735/since-153-breakpoints-dont-work-when-the-charset-o.html^0|1W|C|1I|C|0|2U|R|1|0|U|C|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@$9|W|A|X|1|Y]|$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|15|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]|R|$5|M|N|O|E|$P|S]]]]

A new way to get this problem has appeared as of Visual Studio 2017 15.3.1 through 15.3.5. If you are using <a href="http://editorconfig.org/" rel="nofollow noreferrer">EditorConfig</a>, the <code>charset=utf8</code> option causes these symptoms. The VS team has reproduced this and <a href="https://developercommunity.visualstudio.com/content/problem/100735/since-153-breakpoints-dont-work-when-the-charset-o.html" rel="nofollow noreferrer">says they are working on it</a>.

So one fix is to comment out your <code>charset=utf8</code> line in the .editorconfig file.

Edit: This should be fixed as of VS 15.5.

blocks|key|1708172|text|如果您正在使用对二进制文件的引用(而不是对项目中代码的项目引用)，并且所引用的已编译二进制文件与计算机上相应的源代码不同步，也经常会发生这种情况。这可能是因为您从源代码管理下载了一个新版本的二进制文件而没有附带新的源代码，或者您的机器上有几个版本的二进制文件并且引用了旧的副本，等等。如果这确实是问题所在，那么就有一个很好的理由来尽可能多地使用项目引用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1708173|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This happen often also if you are using a file references to binaries (instead of project references to code in your project), and the compiled binary that you are referencing falls out of sync with the corresponding source code on your machine. This can happen because you downloaded a new version of the binary from source control without the new source code that went with it, or you have a few versions of the binary on your machine and are referencing an old copy, etc. If this is indeed the problem, it's a good reason to use project references as much as it practical.

blocks|key|1473026|text|对我来说，这些项目都没有解决问题。我刚刚在该函数中添加了一行新代码，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1473027|int+a=0;|code-block|syntax|javascript|1473028|通过添加该函数，我猜我触发了visual+studio将此函数添加到原始版本中。|1473029|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

For me, none of the items solved the issue. I just added a new line of code inside that function, something like:

<pre><code>int a=0;
</code></pre>

by adding that, I guess I triggered visual studio to add this function to the original version

blocks|key|5236798|text|我只是重新加载，清理和重建工作对我来说。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5236799|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I just reloaded, clean and rebuilt works for me.

blocks|key|1708248|text|当系统时间在调试过程中或调试会话之间发生更改时，无论是以编程方式、手动方式还是通过外部程序，都可能发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1708249|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This can happen when the system time changes while debugging or between debug sessions, be it programmatically, manually or by an external program.

blocks|key|1708942|text|问题是您的调试信息与程序集不同步。解决方案很简单：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1708943|请转到您的bin文件夹，然后删除files|1708944|Rebuild|unordered-list-item|1708945|
++.pdb|1708946|应该能起到作用！|1708947|(奇怪的是，不丢弃.pdb文件的重建并不总是有效的。我可以看到修改日期正在更新，但仍在链中的某处(VS2013调试器、IIS、程序集缓存)未检测到此更改)|1708948|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|R|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|S|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|T|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|N|$]]

The problem is that your debug info is not in sync with your assembly. The solution is simple:

<ol>
<li>Go to your bin folder</li>
<li>Remove the .pdb files</li>
<li>Rebuild</li>
</ol>

Should do the trick!

(the weird thing is, a rebuild without throwing away the .pdb files doesn't always work. I can see the modified date being updated, but still somewhere in the chain (VS2013 debugger, IIS, assembly cache) this change is not detected)

blocks|key|1709090|text|有一个几乎不可察觉的设置为我解决了这个问题。如果存在断点未命中的特定源文件，则可以将其列在|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1709091|1709092|解决方案资源管理器|unordered-list-item|1709093|右键单击Solution+|1709094|属性|1709095|通用属性|1709096|调试源文件|1709097|“请勿查找这些源files".|1709098|1709099|1709100|1709101|1709102|1709103|​|1709104|1709105|1709106|1709107|1709108|出于某些我不知道的原因，VS2013决定在那里放置一个源文件，随后，我无法再命中该文件中的断点。这可能是“源代码与原始版本不同”的罪魁祸首。|1709109|entityMap^0|0|0|1|2|3|4|4|4|3|2|1|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|16|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|17|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|18|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|19|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|1A|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|1B|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1H|8|@]|9|@]|A|$]]|$1|W|3|V|5|6|7|1I|8|@]|9|@]|A|$]]|$1|X|3|V|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Y|3|V|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Z|3|V|5|6|7|1L|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1M|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|13|$]]

There is an almost imperceptible setting that fixed this issue for me. 
If there is a particular source file in which the breakpoint isn't hitting, it could be listed in 

<ul>
<li>Solution Explorer
<ul>
<li>right-click Solution
<ul>
<li>Properties
<ul>
<li>Common Properties
<ul>
<li>Debug Source Files
<ul>
<li>"Do not look for these source files".</li>
</ul></li>
</ul></li>
</ul></li>
</ul></li>
</ul></li>
</ul>

For some reason unknown to me, VS 2013 decided to place a source file there, and subsequently, I couldn't hit breakpoint in that file anymore. This may be the culprit for "source code is different from the original version".

blocks|key|3820171|text|我同意VS2019中的这个错误，我认为它是在Windows时钟改变时开始发生的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3820172|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I'm with this error in VS2019 and I think that it starts to occurs when Windows has clock changed.

blocks|key|3819493|text|如果您的解决方案中有多个项目，请确保将正确的项目设置为StartUp+Project。若要将特定项目设置为解决方案的启动项目，请右击该项目，选择“Set+As+StartUp+Project”。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3819494|在我正确地设置了我的StartUp项目之后，线程到达了所需的断点。|3819495|entityMap^0|R|F|21|M|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

If you have more than one projects in your solution, then make sure that the correct project is set as the <code>StartUp Project</code>. To set a particular project as the Startup Project of your solution, Right-click the project, choose <code>Set As StartUp Project</code>.

After I set my StartUp Project correctly, desired break-point was reached by the thread.

blocks|key|5236517|text|对我来说，解决方案隐藏在项目属性的Advanced+Build+Settings中：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5236518|📷|atomic|5236519|​|5236520|出于未知的原因，它被设置为none：将它设置为full会导致命中断点。|5236521|要打开此对话框，请打开项目属性，然后转到Build，然后选择页面底部的Advanced...按钮。|5236522|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/529ffa9622018a9957cecfd04c2f55bb.png|imageAlt^0|H|N|0|0|1|0|0|0|D|4|N|4|0|K|5|Z|B|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|10|8|@]|D|@$9|11|A|12|1|13]]|E|$]]|$1|I|3|J|5|6|7|14|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V|W|-4]]]]

For me the solution was hidden in the <code>Advanced Build Settings</code> of the project properties:
<a href="https://i.stack.imgur.com/AZ6CU.png" rel="noreferrer"><img src="https://i.stack.imgur.com/AZ6CU.png" alt="enter image description here"></a>

For an unknown reason it was set to <code>none</code>: setting it to <code>full</code> caused the breakpoints to be hit.

To get to this dialog, open the project properties, then go to <code>Build</code>, then select the <code>Advanced...</code> button at the bottom of the page.

blocks|key|5235304|text|当您正在使用激活器并且设置断点的程序集尚未加载时，可能会收到此消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5235305|一旦激活器加载程序集(假设程序集和调试符号是最新的)，断点就会解析。“调试”菜单中的“模块”窗口是一个很好的查看位置。在那里，您也应该查找您的文件所属的程序集。首先检查程序集是否已加载。那么，它是从哪里加载的？然后，是否加载了符号文件。同样，符号文件是从哪里加载的？最后，检查两者的版本。|5235306|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You can get this message when you are using an activator and the assembly you set the breakpoint into has not been loaded yet.

The breakpoint will resolve once the activator loads the assembly (assuming the assembly and debug symbols are up to date). A good place to look at is the modules window in the debugging menu. There you should look for the assembly which your file belongs too. First check that the assembly is loaded. Then, from where is it loaded? Then, is the symbols file loaded. Again, where is the symbols file loaded from? Finally check the versions of both.

blocks|key|1476572|text|当调试一个加载了用某种CLR语言(托管C%2B%2B、C#等)实现的模块的C%2B%2B项目时，也会发生这种情况。在这种情况下，错误消息确实具有误导性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1476573|解决方案是将公共语言运行库(CLR)支持配置属性放到启动项目中，然后重新编译该属性。|1476574|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

This happens also when debugging a C++ project which loads a module that has been implemented with some CLR language (Managed C++, C# etc). In this situation the error message is misleading indeed.
The solution is to put Common language runtime (CLR) support configuration property to the startup project and recompile that.

blocks|key|1476627|text|我也遇到过这种情况。导致我的问题的条件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1476628|1476629|我正在本地运行完整的IIS7实例|unordered-list-item|1476630|我正在将我的软件版本控制到单独的项目中|1476631|1476632|导致此问题的原因是:打开以前的版本(当提示询问我是否要在IIS调试中指向此实例时，我回答“是”)，然后打开当前版本(再次以“是”响应IIS提示)，然后尝试在以前的版本中进行调试。|1476633|为了解决这个问题，我只是关闭并重新打开了先前和预期的版本，再次将其断言为调试源。|1476634|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|R|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

I encountered this as well. The conditions that caused my issue: 

<ul>
<li>I'm running a full IIS7 instance locally</li>
<li>I'm versioning my software into separate projects</li>
</ul>

I had caused this by opening a previous version (VS prompted to ask if I wanted to point to this instance in IIS debugging, I answered 'Yes'), then opening the current version (again responding to the IIS prompt with a 'Yes'), then attempting to debug in the previous version.

To solve, I merely closed and re-opened the previous and intended version, once again asserting it as the debugging source.

blocks|key|5236480|text|我在一个基于vs2017的32位版本中体验到了这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5236481|实际上，这些解决方案对我都不起作用。我重新启动，清理了IDE文件，清理了构建的解决方案，从git+repo中提取并重新构建了解决方案，但无济于事。|5236482|我从nuget中引入了一个64位的依赖项，一旦我使用了程序集，源代码就不再被构建到最终的可执行文件中，而是构建了IDE缓存的源代码。|5236483|我删除了nuget配置，删除了引用的程序集，下载了源代码，手动构建了log4net，对其进行了签名，将其添加到我的项目的文件夹中，添加了对它的引用，并且我能够再次进行调试。|5236484|这是一种痛苦，我希望它能出现在答案列表中，让所有人都能看到。|5236485|编辑:尽管在IDE设置中打开了“生成错误时提示”选项，但在构建过程中没有出现错误。|5236486|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I experienced this in a 32bit build on vs2017. 

Exactly none of the solutions worked for me. I restarted, I cleared IDE files, clean built solution, pulled from git repo and rebuilt the solution to no avail. 

I was pulling in a 64bit dependency from nuget and as soon as I used the assembly, the sources were not being built into the final executable anymore and instead the IDE cached sources were being built. 

I removed the nuget configuration, removed the referenced assembly, downloaded the source, built log4net manually, signed it, added it to a folder in my project, added reference to it, and I was able to debug again.

This was a pain, I hope it gets up in the answers list for all to see. 

Edit: There was no error during build despite having the option "prompt on build error" being turned on in the IDE settings.

blocks|key|1472405|text|尝试在调试模式下运行时禁用并重新设置断点，而不是在启动调试模式之前执行此操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1472406|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Try disabling and re-setting the breakpoint while running in debug mode instead of doing it before launching debug mode.

blocks|key|1708877|text|首先，我从命令行开始尝试；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1708878|从命令行删除临时文件不起作用。|1708879|C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary+ASP.NET+Files>rd+/s根目录|1708880|When+I+disable+"Enable+Just+My+Code"选项在Tools+->+Options+->+Debugging+->+General中禁用“Enable+Just+My+Code”常规选项|offset|length|style|BOLD|1708881|为我解决了的问题。这是一个WCF应用程序，正在尝试调试一个ashx页面。http://blogs.msdn.com/b/zainnab/archive/2010/10/25/understanding-just-my-code.aspx|1708882|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.msdn.com/b/zainnab/archive/2010/10/25/understanding-just-my-code.aspx^0|0|0|0|7|T|0|0|5|10|2A|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Y|8|@$H|Z|I|10|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@$H|12|I|13|J|K]]|9|@$H|14|I|15|1|16]]|A|$]]|$1|N|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

First I tried from command line;

deleting temp files from command line did work.

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files>rd /s root

When I disable "Enable Just My Code" option in Tools -> Options -> Debugging -> General

The problem resolved for me. It is a WCF application, was trying to debug an ashx page.
<a href="http://blogs.msdn.com/b/zainnab/archive/2010/10/25/understanding-just-my-code.aspx" rel="nofollow">http://blogs.msdn.com/b/zainnab/archive/2010/10/25/understanding-just-my-code.aspx</a>

blocks|key|3819770|text|在我将现有文件添加到项目中之后，它恰好发生在Visual+Studio+2017上。这对我很有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3819771|关闭解决方案，然后转到SolutionFolder\.vs\SolutionName\v15\sqlite3++remove++solution+|offset|length|style|CODE|3819772|ordered-list-item|3819773|3819774|entityMap^0|0|B|17|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@$D|O|E|P|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|I|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

It happenned to be on Visual Studio 2017 after I added existing files to the project. This worked for me:

<ol>
<li>close the solution, </li>
<li>go to <code>SolutionFolder\.vs\SolutionName\v15\sqlite3</code> and remove <code>storage.ide</code></li>
<li>open the solution again</li>
</ol>

blocks|key|1709492|text|我在一个分层架构项目中的几个项目中遇到了同样的问题，问题出在配置中，所选项目的构建复选框未被选中。因此，这个问题已经为一个项目修复了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1709493|对于另一层，即使在配置中启用了构建，它也会带来同样的麻烦。我做了所有其他的选择，比如重新开始清理项目，但没有一个有帮助。最后，我取消选中该特定项目的build复选框，并进行清理和重建。再次选中复选框并执行相同的操作。然后这个问题就解决了。|1709494|希望这能帮上忙..|1709495|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I had the same issue in several projects in a layered architecture project and the problem was in configurations the build check box for the selected project hasn't been checked. so the issue was fixed for one project.

For one other layer it was giving this same trouble even the build is enable in the configurations. I did all the other options like restarting cleaning the project but non of them helped. Finally I unchecked the build checkbox for that particular project and cleaned and rebuild. the again marked the checkbox and did
the same. then the issue was fixed.

Hope this helps..

blocks|key|1472365|text|对我来说起作用的是将解决方案平台从x86更改为任何CPU。在切换到Any之后，我设置了一个停止地址，运行网站，打开页面，点击按钮，它就停止了。我关闭了站点，改回了x86，并成功地执行了相同的序列。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1472366|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

What worked for me was to change the solution platform from x86 to Any CPU. After changing to Any, I set a stop address, ran the website, opened the page, clicked the button and it stopped. I closed the site, changed back to x86 and performed the same sequence successfully.

blocks|key|3818962|text|在我的例子中，我在VS2012中附加了一个正在运行的进程。附加时，您可以选择在各种模式下进行调试(本机、脚本、silverlight、托管2.0、托管4.0等)。默认情况下，调试器会自动选择该模式。然而，Automatic并不总是做出正确的选择。如果您的进程包含多种类型的代码，请确保调试器使用了正确的代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3818963|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, I was attaching to a running process in VS 2012. When attaching, you're given the option to debug in various modes (native, script, silverlight, managed 2.0, managed 4.0, etc). By default, the debugger selects the mode automatically. However Automatic does not always make the correct choice. If your process contains multiple types of code, be sure the debugger is using the correct one.

blocks|key|5235514|text|在我的例子中，我正在开发一个Windows+CE应用程序，该应用程序在仿真器上进行了测试。问题是可执行文件没有部署到仿真器，因此.pdb+(在开发环境中)与.exe+(在仿真器中)不同步，因为新的.exe从未复制到仿真器。我不得不删除模拟器中的.exe以强制进行新的部署。然后它就成功了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5235515|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, I was developing a Windows CE app, that tested against an emulator. The problem was that the executable wasn't deployed to the emulator, so the .pdb (in the development environment) was out of sync with the .exe (in the emulator), because the new .exe was never copied to the emulator. I had to delete the .exe in the emulator to force a new deployment. Then it worked.

blocks|key|3819038|text|在Windows7，Visual+Studio+Express+2010中，如果您已经为Windows+XP+SP3激活了“使用兼容模式”选项，则可能会发生此错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3819039|我取消选中该选项，它再次完美地工作。右键单击VS或可执行文件的快捷方式，选择属性，然后选择compatibility.|offset|length|style|BOLD|3819040|entityMap^0|0|12|2|19|D|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|I|$]]

Under Windows 7, Visual Studio Express 2010, if you have activated the option Use compatibility mode for Windows XP SP3, this error may occur. 

I unchecked the option and it worked perfect again. Right-click on the shortcut to VS or the executable, select properties and then compatibility.

blocks|key|1708897|text|这发生在我身上，因为我在解决方案中有其他没有构建的项目。卸载这些有问题的项目(在解决方案资源管理器->+Unload+project中右键单击该项目)之后，重新构建解决方案并再次运行--中断点被击中！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1708898|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It happened to me because I had other projects in the solution that weren't building.
After I unloaded those problematic projects (right-click on the project in the solution explorer -> Unload Project), rebuilt the solution and ran again -- the breakpoint was hit!

blocks|key|1473012|text|当您尝试调试时，请确保您未处于发布模式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1473013|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Make sure you are not in Release Mode when you try to debug.

blocks|key|3819979|text|面向VS代码用户的：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3819980|如果您在尝试调试ASP.NET+.NET核心应用程序时遇到此问题，请确保在tasks.json中定义的生成任务成功运行，并且您可以在调试控制台窗格中看到其输出。|CODE|3819981|由于某种原因(至少在某些情况下)，引用此任务的launch.json中定义的调试配置将继续执行定义的二进制文件，即使构建任务失败，而且由于构建任务已失败，该二进制文件将成为最后一个成功构建的程序集。|3819982|entityMap^0|9|1|0|11|A|0|N|B|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|P|8|@$9|Q|A|R|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|S|8|@$9|T|A|U|B|H]]|D|@]|E|$]]|$1|K|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|L|$]]

For VS Code users:

If you hit this while trying to debug an ASP .NET Core application, make sure that the build task defined in <code>tasks.json</code> and whose output you can see in the Debug Console pane, runs successfully.

The debugging configuration defined in <code>launch.json</code> which references this task, will for some reason (at least under some circumnstances) continue to execute the defined binary even if the build task has failed, and since the build task has failed, that binary is going to be the last successfully built assembly.

blocks|key|1473069|text|故意中断构建，这意味着在项目中添加一些在调试时不同步的任意文本。尝试调试并接收异常。现在修复异常并调试项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1473070|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Intentionally break the build, meaning add some arbitrary text in the project that is out of sync when debugging. Attempt to debug and receive the exception. Now fix the exception and debug the project.

blocks|key|1477218|text|帮助我的步骤(VS+Community+2017，15.9.11)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1477219|请注意，执行以下步骤后，断点将丢失。|1477220|1477221|右键单击类文件和选定的类文件并从Project|ordered-list-item|1477222|Right中排除单击项目并选择Add+File|1477223|Navigated和<>E112>Existing+File|1477224|Navigated以选择有问题的类文件|1477225|1477226|1477227|entityMap^0|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|G|7|X|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|Q|$]]

Steps that helped me (VS Community 2017, 15.9.11).

Note that breakpoints will be lost after doing steps below.

<ol>
<li>Right clicked on the class file </li>
<li>Selected Exclude From
Project</li>
<li>Right clicked on the project</li>
<li>Chose Add and Existing File</li>
<li>Navigated to pick the class file in question</li>
</ol>

blocks|key|1709716|text|我已经尝试了提出的解决方案，但它不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1709717|如果您有多个项目，请将要调试的项目设置为启动项目。|1709718|​|1709719|📷|atomic|offset|length|1709720|1709721|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/42b29e5e0b68c195c9ec6e22f064649d.png|imageAlt^0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@$I|Y|J|Z|1|10]]|A|$]]|$1|K|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

I've tried the proposed solutions but it didn't work.

In case you have multiple project, make the one you want to debug as the startup project.

<a href="https://i.stack.imgur.com/85ErH.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/85ErH.png" alt="enter image description here"></a>

blocks|key|1477346|text|退出VS。->删除.vs文件夹。->开放VS.->运行项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1477347|上面的解决方案对我很有效。希望这也能对你有所帮助。|1477348|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Exit from VS. -&gt; Delete the .vs folder. -&gt; Open VS. -&gt; Run the Project.
Above solution worked for me. Hope this will help you as well.

blocks|key|1473235|text|它运行良好-您必须取消选中复选框"Enable+Just+My+Code“，如下图所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1473236|​|1473237|📷|atomic|1473238|1473239|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/0a885bbbb3934f7cadb84c62a16c01cd.png|imageAlt^0|H|J|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|K|3|G|5|6|7|12|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S|T|-4]]]]

It works well - you must put unchecked in the checkbox &quot;Enable Just My Code&quot; as highlighted in below image:
<a href="https://i.stack.imgur.com/JSF6E.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/JSF6E.png" alt="enter image description here" /></a>

blocks|key|3819112|text|如果被调试的进程包含多个appdomain，并且程序集被加载到这两个appdomain中，并且其中一个正在加载旧副本(通常是动态加载的内容，如插件)，则断点可能看起来是实心的，但应该命中断点的线程位于具有旧程序集的appdomain中，并且永远不会命中。您可以在模块窗口中看到加载了哪些程序集及其路径。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3819113|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If your debugged process contains multiple appdomains and the assembly is loaded into both, and one of them is loading an old copy (usually something dynamically loaded like a plugin) the breakpoint can appear solid, but the thread that should hit the breakpoint is in the appdomain with the old assembly, and never hits. You can see what assemblies are loaded and their path in the module window.

blocks|key|1472821|text|检查解决方案中是否有多个同名文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1472822|这是我从别人手中接过的一个项目。断点列表中充满了Controller.cs中的行号，有些是活动的，有些不是。我发现了这个问题，并尝试了一些选项，但当我双击断点时，它们将我带到解决方案中的不同项目。因为这两个文件的名称是相同的，所以它们看起来是相同的，但事实并非如此。答案当然是忽略警告，因为如果你加载另一个文件，它们将变为活动状态。|1472823|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Check to see if you have more than one file with that name in the solution.

I had this on a project that I took over from someone else. The breakpoint list was full of line numbers in Controller.cs, some active and some not. I found this question, and tried a few options, but when I double-clicked on the breakpoints, they took me to different projects within the solution. Because the files were called the same, they appear to be the same, but they aren't. The answer is of course then to ignore the warning, as they will become active if you get to load that other file.

blocks|key|5236301|text|请转至：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5236302|5236303|工具>选项>调试>常规>取消选中“要求源文件与原始版本完全匹配”|blockquote|offset|length|style|BOLD|5236304|5236305|entityMap^0|0|0|C|4|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@$F|P|G|Q|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

go to:

<blockquote>
 Tools > Options > Debugging > General > unchecked "Require source
 files to exactly match the original version"
</blockquote>

blocks|key|3819936|text|也许dlls是从GAC加载的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3819937|您可以从gac卸载dll，需要管理员权限。|3819938|gacutil+-u+YourDll|3819939|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Maybe the dlls are being loaded from GAC.

You can uninstall the dll from gac, admin permission are required.

gacutil -u YourDll

blocks|key|1473074|text|我在VSCode中遇到了这个问题，问题是我在编辑器中查看的文件与项目正在构建的文件的副本不同。我已经将C#库的存储库克隆到两个位置，一个是在编辑器中打开的，另一个是由项目链接的。如果干净的构建不适合您，请检查您是否在编辑器中查看文件的正确副本！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1473075|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had this problem in VSCode, and the issue was that the file that I was looking at in the editor was not the same copy of the file that the project was building. I had cloned a repository for a C# library down into two locations, one which was open in the editor and one which was being linked by the project. If clean building isn't working for you, check that you are looking at the right copy of the file in the editor!

blocks|key|5236724|text|我修复了这个问题，首先删除了有问题的文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5236725|编译。|5236726|出于某种原因，程序无论如何都会运行。它不应该编译。它有错误和东西，但它仍然可以运行。|5236727|我读了有问题的文件。再跑一次。不知何故它自我修复了。|5236728|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I fixed that by first removing the file that's problematic.

Compile.

For some reason the program runs anyway. It shouldn't compile. It has errors and stuffs but it runs anyway. 

I readd the file in problem. Run again. Somehow it fixed itself.

blocks|key|5236744|text|因为build的版本更改了(很可能是您修改了源代码)，所以重新编译解决方案并再次运行应用程序，之后它将达到调试断点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5236745|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Because build's version changed (most probably you modified the source code), so recompile the solution and run the application again, after then it will hit debug break point.

blocks|key|1709652|text|我的问题有点愚蠢。我有我的项目的两个副本，我在visual+studio中混合了文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1709653|假设你有projectX和projectY。这两个项目都包含myFile.cs。我打开了projectX并编辑了myFile.cs。但是这个myFile.cs是属于projectY的。(可以在visual+studio中打开来自不同项目的文件)，因此在这种情况下，警告说源代码将与原始代码不同。|offset|length|style|CODE|1709654|entityMap^0|0|4|8|D|8|U|9|18|8|1K|9|1Y|9|2A|8|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]|$D|P|E|Q|F|G]|$D|R|E|S|F|G]|$D|T|E|U|F|G]|$D|V|E|W|F|G]|$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|I|$]]

My issue was a bit stupid. I had two copy of my project and I mixed files in visual studio. 

Let s say you have <code>projectX</code> and <code>projectY</code>. These projects both contain <code>myFile.cs</code>. I opened <code>projectX</code> and edited <code>myFile.cs</code>. But this <code>myFile.cs</code> was belong to <code>projectY</code> . (It s possible to open files from different projects in visual studio) So in that case as warning says source code will be different than original.

blocks|key|1473221|text|有时您只需要将解决方案配置从“发布”更改为“调试”即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1473222|📷|atomic|offset|length|1473223|​|1473224|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/6340f414883473e9488ba8ecfffc1216.png|imageAlt^0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@$E|T|F|U|1|V]]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P|Q|-4]]]]

Sometimes you just need to change Solution configuration from 'release' to 'debug'.<a href="https://i.stack.imgur.com/WDth8.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/WDth8.png" alt="enter image description here" /></a>

blocks|key|3819081|text|在我的例子中，问题是在项目properties>>Web下没有启用ASP.NET调试|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3819082|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case the problem was ASP.NET debugging wasn't enabled under project properties>>Web

blocks|key|5235865|text|在我的例子中，我忘记在声明模板函数的头文件中包含"stdafx.h“。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5235866|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case I forgot to include the "stdafx.h" in the header file where I was declaring a template function.

blocks|key|1709043|text|我之前一直在摆弄我的csproj文件。因此，在项目属性(VS2013)>+Web标签>+Servers部分>+dropdown下，当我之前选择了"Local+IIS“时，我选择了"IIS+Express”。一旦我将设置更正为以前的设置，断点就可以工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1709044|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had been messing with my csproj file earlier. So under project properties (VS 2013) > Web tab > Servers section > [dropdown], I had "IIS Express" selected when I previously had "Local IIS" selected. Once I corrected the settings to what I had before, the breakpoints worked.

blocks|key|5236237|text|有些情况下，重新编译和重新编译并不能帮助解决这个问题。其他可能的解决方案之一可能是从解决方案资源管理器中删除带有断点的源文件，然后重新添加它(例如，通过从文件夹中拖放)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5236238|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

There are cases when recompiling and rebuild doesn't help to overcome this problem.
One of other potential solutions could be deletion of source file with breakpoints from Solution Explorer and adding it again (e.g. by drag and drop from folder).

blocks|key|1709213|text|对我来说，我的网站在默认网站(http://localhost/myapp/)下的IIS应用程序中运行，IIS应用程序的映射指向与我正在处理的源代码不同的磁盘路径。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1709214|若要解决此问题，请将IIS应用程序重新映射到与要生成的源代码相同的路径。|1709215|(如果您在磁盘上的不同位置运行同一应用程序的多个版本，则会发生这种情况)|1709216|entityMap|0|LINK|mutability|MUTABLE|url|http://localhost/myapp/^0|F|N|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

For me; my website was running in an IIS Application under Default Website (<a href="http://localhost/myapp/" rel="nofollow">http://localhost/myapp/</a>) and the mapping for the IIS application was pointing to a disk path that was different to the source code I was working on. 

To resolve; remap your IIS Application to the same path as the source code you are building.

(This can happen if you have multiple versions of the same application running from different locations on your disk)

blocks|key|5236542|text|VS+2017的一些版本(与.editorconfig结合使用)也有一个问题：Since+15.3,+breakpoints+don't+work+when+the+charset+of+the+file+is+not+the+same+as+the+one+in+.editorconfig+(utf8+or+utf8-bom)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5236543|entityMap|0|LINK|mutability|MUTABLE|url|https://developercommunity.visualstudio.com/content/problem/100735/since-153-breakpoints-dont-work-when-the-charset-o.html^0|13|3I|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Also there is an issue with some versions of VS 2017(in combination with .editorconfig): <a href="https://developercommunity.visualstudio.com/content/problem/100735/since-153-breakpoints-dont-work-when-the-charset-o.html" rel="nofollow noreferrer">Since 15.3, breakpoints don't work when the charset of the file is not the same as the one in .editorconfig (utf8 or utf8-bom)</a>

blocks|key|1709544|text|在我的例子中，其他建议都不起作用，但是重新克隆我的存储库使这个问题消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1709545|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, none of the other suggestions worked, however recloning my repository made this issue disappear.

blocks|key|1709547|text|在将一个项目从netcoreapp2.0升级到netcoreapp2.2之后，我遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1709548|我只是通过编辑.csproj文件中的TargetFramework条目来完成此操作，而忽略了也将更改设置为launch.json。|offset|length|style|CODE|1709549|"program":+"${workspaceFolder}/src/MyProject/bin/Debug/netcoreapp2.0/MyProject.dll"|code-block|syntax|javascript|1709550|这意味着VS+Code总是加载项目的旧2.0版本。我只是在删除了/bin和/obj中的所有内容后才发现它，然后它根本不会运行，直到我在上面的路径中发现了2.0。|1709551|entityMap^0|0|7|7|I|F|1H|B|0|0|W|4|11|4|24|3|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$D|10|E|11|F|G]|$D|12|E|13|F|G]|$D|14|E|15|F|G]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|P|$]]

I got this problem after upgrading a project from netcoreapp2.0 to netcoreapp2.2.

I'd done this just by editing the <code>TargetFramework</code> entry in the <code>.csproj</code> file and neglected to also make the change <code>launch.json</code>.

<pre><code>"program": "${workspaceFolder}/src/MyProject/bin/Debug/netcoreapp2.0/MyProject.dll"
</code></pre>

This meant that VS Code was always loading the old 2.0 version of the project. I only discovered it after deleting everything in <code>/bin</code> and <code>/obj</code> and then it wouldn't run at all until I spotted the <code>2.0</code> in the path above.

blocks|key|5236658|text|我遇到了这个问题，这是因为我们的DevOps团队需要设置Azure+Cloud。在开发时，只需将其从Web.config中删除即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5236659|<httpRuntime+maxRequestLength="102400"+/>

++++
++++|code-block|syntax|javascript|5236660|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I had this problem and that was because of a required Azure Cloud setting requirement from our DevOps team. When developing simply leave it out of the Web.config.

<pre><code>&lt;httpRuntime maxRequestLength="102400" /&gt;

 &lt;!--TODO #5 comment out for IIS Express fcnMode goes with httpRunTime above in other environment just in DEV --&gt;
 &lt;!--fcnMode="Disabled"/&gt;--&gt;
</code></pre>

blocks|key|1709571|text|在我的例子中，给静态类中的静态约束字符串字段分配了大约120kb的base64值。之后，这个问题就出现了。我尝试了很多解决方案，但直到我删除了这个繁重的任务，问题才得到解决。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1709572|我的环境:+MS+VS+Community+2017版本15.9.16|1709573|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In my case, I was assigned approx 120kb base64 value to a static constraint string field in a static class. After then this problem occurred. I was tried a lot of solutions but the problem was not solved until I removed this heavy loaded assignment.

My environment:
MS VS Community 2017
Version 15.9.16

blocks|key|1473091|text|我在使用Local+IIS而不是IIS+express时遇到了这个问题。IIS中的文件源确实与Visual+Studio中的源文件相匹配，但是，我必须回收IIS中的应用程序池，以便让它使用新构建的DLL。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1473092|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I ran into this issue when using Local IIS rather than IIS express. The source of the files in IIS did match those in Visual Studio, however, I had to Recycle the Application Pool in IIS in order to have it consume the freshly built DLLs.

blocks|key|5237138|text|尽管有所有的答案，但我的问题实际上与这里提到的都不同！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5237139|确保您的属性->+Build选项卡->输出路径与您选择的构建配置的解决方案中的所有其他项目指向相同的位置！|5237140|​|5237141|📷|atomic|offset|length|5237142|5237143|如果您的启动项目将其可执行文件发送到与您尝试调试的dll不同的文件夹中，那么尽管您的构建和visual+studio工作得很好，您仍可能会遇到问题。|5237144|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/64e7c946a6b11dbb562494c6c7b743fc.png|imageAlt^0|0|0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@$I|10|J|11|1|12]]|A|$]]|$1|K|3|E|5|6|7|13|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U|V|-4]]]]

Despite all the answers, my issue was actually different from all mentioned here!
Make sure your Properties -&gt; Build tab -&gt; Output path is pointing to the same place as all the other projects in your solution for the build configuration you have selected!
<a href="https://i.stack.imgur.com/6rZ7c.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/6rZ7c.png" alt="enter image description here" /></a>
If your startup project is sending it's executable to a different folder from the dll you're trying to debug, you might have issues despite your build and visual studio working perfectly.

blocks|key|1477437|text|对于类似的问题，我执行了以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1477438|从菜单调试->选项->常规中取消选中“仅启用我的代码”选项|1477439|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I did the below for a similar issue:
Uncheck the option &quot;Enable Just My Code&quot; from the menu Debug -&gt; Option -&gt; General

blocks|key|1476644|text|我最近受到了这个问题的困扰，在我的案例中，我将问题追溯到我在测试时所做的事情:更改系统时间。我并不是说这对每个人都适用，但我想我应该提一下，因为它还没有被提到过。如果你开始在调试版本之间移动时钟，那么它可能会对创建各种文件的顺序感到非常困惑-我只能假设它使用文件修改日期来确定源代码是否有效，以及它需要重新编译哪些二进制文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1476645|也可以选择重新保存web.config以缩短其修改时间。|1476646|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I suffered from this recently, and in my case I traced the problem back to something I was doing when testing: changing the system time. I'm not suggesting this is the case for everyone, but thought I'd mention it since it hasn't been mentioned already. It appears if you start moving the clock around between debug builds then it can get very confused about what order various files have been created it - I can only assume it is using file modified dates to determine if the source code is valid or not, and which binaries it needs to recompile.

It is also an option to re-save web.config to bump its modification time.

blocks|key|1709284|text|我刚刚重启了computer，它对我很有效。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1709285|entityMap^0|3|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Me just restarted computer and it worked greatly for me.

blocks|key|1476758|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1476759|📷|atomic|offset|length|1476760|1476761|我发现当断点在不能中断的行上时，就会发生错误。我没有显示工具提示，是为了在没有那个错误后直接显示线条。|1476762|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/4bd50aecdfafda3adea356da671d70da.png|imageAlt^0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@$E|U|F|V|1|W]]|A|$]]|$1|G|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

<img src="https://i.stack.imgur.com/gkaJP.png" alt="code causing the &quot;The source code is different&quot; error">

I found the error occurred when a breakpoint is on a line that can't be broken on. I didn't show the tool-tip in effort to show the line directly after does not have that error.

When debugging in Visual Studio, sometimes I add a breakpoint but it's hollow and VS says "The breakpoint will not currently be hit. The source code is different from the original version." Obviously this prevents me from being able to debug.

What on earth does the message mean? What original version? If I've just opened up the solution and not made any changes whatsoever to the code, how can there be an 'original version'?

"The breakpoint will not currently be hit. The source code is different from the original version." What does this mean?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在Visual Studio中调试时，有时我会添加一个断点，但它是空的，VS会说“断点当前不会命中。源代码与原始版本不同。”显然，这会阻止我进行调试。这条信息到底是什么意思？什么原始版本？如果我只是打开了解决方案，而没有对代码做任何修改，怎么会有“原始版本”呢？

问“当前不会命中断点。源代码与原始版本不同。”这是什么意思？
EN

回答 63

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问“当前不会命中断点。源代码与原始版本不同。”这是什么意思？EN

回答 63

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问“当前不会命中断点。源代码与原始版本不同。”这是什么意思？
EN