“转到定义”在Visual Studio只带来了非项目引用元数据 [英] “Go To Definition” in Visual Studio only brings up the Metadata for Non-Project references

问题描述

我有一个包含在DLL格式的程序集的引用C＃项目。我对这些DLL文件的PDB信息，包含在同一文件夹中。当我按引用的成员F12，我想去成员的定义。相反，它给我的元数据，当然我不想要的。

I have a C# project which contains references to assemblies in DLL format. I have the PDB information for these DLL files, contained in the same folder. When I press F12 on a referenced member, I want to go to the definition of the member. Instead, it gives me the metadata, which of course I don't want.

当VS是调试，但它到源代码，如果我单步成方法。但是，如果我按这个方法F12，它仍然使我的元数据。

When VS is debugging, it does go to the source code if I single step into that method. But if I press F12 on that method, it still brings me to the metadata.

有一个类似的问题在这里，但它仅适用于项目引用，并接受的解决方案无关，与我的问题。

There is a similar question here, but it only applies to project references, and the accepted solution has nothing to do with my issue.

" GO要定义"在Visual Studio不仅带来了元数据

要总结：

• 引用的项目是一个DLL


• 我有PDB信息


• 单步调试模式使我的源代码


• F12使我对元数据


• 我要F12带我去为调试做的源代码。

• Referenced project is a DLL
• I have the PDB information
• Single-stepping in debug-mode brings me to the source code
• F12 brings me to metadata
• I want F12 to bring me to the source code as debug does.

编辑：添加一个项目是不是一种选择，因为它创造了额外的复杂性是我们大约五这些都是在单独的源控制库等项目解决方案文件的引用。

Adding as a "Project" is not an option as it creates additional complexity as our solution file references about five other projects which are all under separate source control repositories.

推荐答案

看来，这个问题已在Visual Studio 2013年有在同一文件夹中的PDB信息作为DLL是解决了显示我的源代码，当我使用转到定义。我没有安装反射器扩展。

It appears that this issue has been solved in Visual Studio 2013. Having the PDB information in the same folder as the DLL is showing me the source code when I use Go To Definition. I do not have the Reflector extension installed.

这篇关于“转到定义”在Visual Studio只带来了非项目引用元数据的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！