blocks|key|4410657|text|检查存储CS文件的物理目录，可能有两个单独的文件，如果没有，请在文本编辑器(而不是VS)中打开.csproj。查看该文件是否被引用了两次。如果是这样，只需删除其中一行。如果这不起作用，您可以按照它所说的做，并设置断点位置:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4410658|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|$]]

Check the physical directory the CS file is stored in, there may be two seperate files, and if not open the .csproj in a text editor (not VS). See if the file is referenced twice. If so, just delete one of the lines. If that doesn't work, you could always do what it says and set the breakpoint location :)

blocks|key|4410493|text|我发现了问题，原来IIS被配置为使用我备份文件夹中的项目的不同副本。这听起来很愚蠢，但如果有人有类似的东西，我会保留这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4410494|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 found the issue, it turns out IIS was configured to use a different copy of the project I had in my backup folder. It sounds pretty silly but I'll keep this question open if someone had something similar.

blocks|key|4410717|text|尝试重新构建解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4410718|有时会有post-build脚本将DLLs从一个项目复制到另一个项目，以便在不同的项目中保持DLL的更新。如果您只修改和编译一个项目，那么这些脚本中的一些可能不会被执行，并且旧的DLLs可能不会更新。|offset|length|style|CODE|4410719|entityMap^0|0|4|A|H|4|2H|4|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]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|I|$]]

Try rebuilding the solution. 

Sometimes there are <code>post-build</code> scripts that copy the <code>DLLs</code> from one project to another in order to keep the DLLs updated in different projects. If you modify and compile just one project, then some of these scripts might not be executed and the old <code>DLLs</code> might not be updated.

blocks|key|4410574|text|如果有人遇到同样的问题，请转到iis，然后选择左侧的应用程序池，然后选择您的应用程序池，然后在右侧单击查看应用程序。现在，在物理路径下，您将能够看到虚拟路径映射到的物理路径，因此请确保物理路径指向正确的文件夹，如果没有指向正确的文件夹，则从应用程序池中删除您的应用程序并重新添加|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4410575|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|$]]

Incase someone is having the same issue, go to iis, then application pools on the left then select your application pool then on the right click on View Applications. Now under physical path you will be able to see the physical path to which your virtual path is mapped to, so make sure the physical path is pointing to the right folder and if incase it is not pointing to the right folder then remove your application from the app pool and add it again

blocks|key|4410621|text|当您尝试从根(项目的根)文件夹复制成功生成的项目并将其副本保存到相应Visual+Studio的"+project“文件夹中时，调试项目会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4410622|执行上述步骤时，Visual+Studio调试位置有时会保持对复制/备份文件夹中生成的DLL的引用。|4410623|同样，可以通过此处编写的方法之一进行更改。|4410624|但是，如果您使用的是Visual+Studio的内置IIS-+Express，那么您需要导航到项目属性"Properties%7Calt%2Benter“=>+"Web”=>中的Servers部分，选择IIS+Express+=>作为当前项目的URL，单击“创建虚拟目录”。|4410625|这将警告您当前的项目Url已被某个其他项目位置(您的副本%7C备份文件夹)引用，请确认您在对话框中的选择，此时您将再次命中断点。|4410626|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

This happens to a debugging project when you try copying successfully built project from root(project's root) folder and saving the copy of same in "Project" folder of your respective Visual Studio.

When you do the above step, Visual Studio debugging location sometimes keep referencing to the built DLLs in the copy/back-up folder.

The same can be changed BY ONE OF THE METHODS written here. 

But if you are using Visual Studio's built-in IIS-EXPRESS, then you need to navigate to project properties "Properties|alt+enter" => "Web" => In Servers Section, select IIS Express => For current Project URL, click "Create Virtual Directory".

This will warn you that the current Project Url is referred by some other Project Location(Your Copy|back-up Folder), Confirm your selection for the dialog box, and there you are, as HITTING your breakpoints again.

blocks|key|4410670|text|这可能是由于您的链接中指向了错误的库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4410671|当我遇到这个问题时，我刚刚用一个旧项目开始了一个新的解决方案。我没有在Project->link->input部分更改目标库。所以一旦我做了更改，我就会得到这个错误。每个解决方案都保留一个库的副本。|4410672|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 can be due to pointing to the wrong library in your link. 

When I got this problem, I had just started a new solution with an old project. I had not changed the target library in the Project->link->input section. So as soon as I made changes, I got this error. Each solution keeps a copy of the library.

blocks|key|4410696|text|我也遇到了同样的问题，我决定删除类上的[System.Diagnostics.DebuggerStepThroughAttribute()]属性。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4410697|entityMap^0|J|1F|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|$]]

I had the same trouble and decided it by deleting attribute <code>[System.Diagnostics.DebuggerStepThroughAttribute()]</code> on the class.

blocks|key|4410965|text|当您调试与项目中的另一个文件同名的.cshtml文件时，可能会发生这种情况。调试器选择其中一个文件作为正确的匹配项(似乎是随机的)，因此在将临时ASP.NET文件中的文件与项目中的源代码进行比较时，调试器通常会发现不匹配的文件。在我的例子中，解决方案是将Standard.cshtml中的一个或两个文件重命名为更具体的名称。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4410966|entityMap^0|H|7|3J|F|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

This can happen when you are debugging a <code>.cshtml</code> file with the same name as another file in the project. The debugger picks one of the files as the correct match (seemingly at random), so it will often find a mismatch when it compares the file from the Temporary ASP.NET Files to the source code in your project. The solution in my case was to rename one or both of the files from <code>Standard.cshtml</code> to something more specific.

blocks|key|4410991|text|IIS问题在我的案例中，某人或某个迁移组件更改了我的web应用程序的物理路径(基本设置)。不是指向我在磁盘上的解决方案，而是指向具有较旧版本的应用程序的另一个位置。恢复正确的路径，修复它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4410992|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|$]]

IIS problem in my case, someone or some migration component changed the Physical Path of my web application (basic settings). Was not pointing to my solution on disk, but to another location with an older version of the app. Restoring the proper path, fixed it.

I keep getting this error saying there's a copy of the .cs file hence the break point will not get hit. 

I have tried cleaning solution, rebuilding , deleting the .pdb files in the obj and bin folders, closing VS and restarting it, restarting the whole machine (It's Windows! Sometimes the most complicated, unexplained problems get fixed like this :\ )

Any idea what else I can try? it's a .net project on VS2015

<a href="https://i.stack.imgur.com/pLjAW.png" rel="noreferrer"><img src="https://i.stack.imgur.com/pLjAW.png" alt="Breakpoint error "></a>

"The breakpoint will not currently be hit. A copy of file was found in dll file, but the current source code is different"

我一直收到这个错误，说有一个.cs文件的副本，因此不会命中断点。我已经尝试过清理解决方案，重建，删除obj和bin文件夹中的.pdb文件，关闭VS并重新启动它，重新启动整个机器(这是Windows！有时，最复杂、无法解释的问题会像这样得到解决:\ )你知道我还能试什么吗？这是VS2015上的一个.net项目​​

问当前不会命中断点。在dll文件中找到了文件的副本，但当前源代码不同
EN

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问当前不会命中断点。在dll文件中找到了文件的副本，但当前源代码不同EN