问题描述
我也有类似这样的调用结构工程：
I have a project which has a calling structure similar to this:
- 主要项目/应用程序
- 我的库代码
- 别人的库代码
- 我的库代码
- main project/application
- my library code
- someone else's library code
- my library code
一切都写在C＃和我有获得别人的库代码。他们的代码不包括在我的项目，因为它是开源的，而不是我的代码。我可以让所有的库的调试版本，我已经这样做了。
Everything's written in C#, and I have access to 'someone else's library code'. Their code is not included in my project, because it's open source and not my code. I can make debug versions of all the libraries, and I've done so.
这是别人的库代码（SELC，我猜？）抛出一个异常一个海森 - 错误的一种方式，而我试图追查，也许提交bug修正到项目维护者。问题是，我调试堆栈停在我的库中的代码，并列出了SELC为外部，我不能调试到它。我复制了pdb文件以及调试版本的库到我的应用程序的调试目录中，仍然没有运气;我似乎无法调试到他们的代码，我不能踏进去的。
That 'someone else's library code (SELC, I guess?) is throwing an exception in a heisen-bug kind of way, and I'm trying to track it down and maybe submit a bugfix to the project maintainer. Problem is, my debugging stack is stopping at my library code, and lists the SELC as 'external' and I can't debug into it. I've copied the pdb files as well as the debug version of the library into the debug directory of my application, and still no luck; I can't seem to debug into their code, and I can't step into it at all.
曾几何时，早在VS6日子里，我可以做this--必须在两个不同的环境中同时打开两个不同的项目，并有跟踪调试程序跨边界的DLL从一个项目到另一个。我认为功能仍然存在，因为它只是使党有用的。
Once upon a time, back in vs6 days, I could do this-- have two different projects open at the same time in two different environments, and have the debugger trace across dll boundaries from one project into another. I'd assume that functionality remains, because it's just so dang useful.
有什么建议？
我已经寻找这个答案，但是没有找到，因此，如果这是一种欺骗，只是让我知道去哪里找。
I've looked for this answer but not found it, so if this is a dupe, just let me know where to look.
推荐答案
你已经仅我的代码，在Visual Studio的调试选项是否开启？
Do you have "Just My Code" turned on in Visual Studio's debugging options?
这篇关于跨越的dll C＃调试的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！