I have a VS Solution with some breakpoints. When I attach the solution to a third-party program the breakpoints are omitted ("The breakpoint will not currently be hit. No symbols have been loaded for this document"). Confusingly breakpoints of any (referenced) project that are not within my solution are hit, only those within my own solution are not. So when interacting the third-party tool I cannot debug through my projects. I also tried out this but the problem still occurs. I also re-built the whole solution to re-recreate the DEBUG-information-files for the projects. The location is the same as for the other solutions, but apparently its contained information is not loaded. Any ideas why?
我有一个带有一些断点的VS解决方案。当我将解决方案附加到第三方程序时，会省略断点（“断点当前不会被命中。没有为此文档加载符号”）。令人困惑的任何（引用的）项目的断点都不在我的解决方案中，只有那些在我自己的解决方案中的断点不会。因此，在与第三方工具交互时，我无法通过我的项目进行调试。我也试过了，但问题仍然存在。我还重新构建了整个解决方案，以重新创建项目的DEBUG信息文件。该位置与其他解决方案相同，但显然未加载其包含的信息。有什么想法吗？
1 个解决方案
#1
0
Finally I found the answer in this post. I took a look into the loaded modules (Debug->Windows->Modules while having assembly attached to process) and noticed that my actual assembly wasn´t in the list. The code I wanted to debug is built with .NET 3.5 but modules have only been loaded for .NET 4.0. Usually this might be detected automatically as far as I am concerned but however this time automatic detection did not work for some weird reason so I changed selected code type from managed (v4.0) to managed (v2.0) and now it works. Hope this won´t occur when I have to debug on .NET 4.0 later again...
最后我在这篇文章中找到了答案。我查看了加载的模块（Debug-> Windows-> Modules，同时将程序集附加到进程），并注意到我的实际程序集不在列表中。我想调试的代码是使用.NET 3.5构建的，但模块只是为.NET 4.0加载的。通常这可能会被我自动检测到，但是这次自动检测不能用于某些奇怪的原因，所以我将选定的代码类型从托管（v4.0）更改为托管（v2.0），现在它可以正常工作。希望在以后再次在.NET 4.0上进行调试时不会发生这种情况......
#1
0
Finally I found the answer in this post. I took a look into the loaded modules (Debug->Windows->Modules while having assembly attached to process) and noticed that my actual assembly wasn´t in the list. The code I wanted to debug is built with .NET 3.5 but modules have only been loaded for .NET 4.0. Usually this might be detected automatically as far as I am concerned but however this time automatic detection did not work for some weird reason so I changed selected code type from managed (v4.0) to managed (v2.0) and now it works. Hope this won´t occur when I have to debug on .NET 4.0 later again...
最后我在这篇文章中找到了答案。我查看了加载的模块（Debug-> Windows-> Modules，同时将程序集附加到进程），并注意到我的实际程序集不在列表中。我想调试的代码是使用.NET 3.5构建的，但模块只是为.NET 4.0加载的。通常这可能会被我自动检测到，但是这次自动检测不能用于某些奇怪的原因，所以我将选定的代码类型从托管（v4.0）更改为托管（v2.0），现在它可以正常工作。希望在以后再次在.NET 4.0上进行调试时不会发生这种情况......