All geek questions in one place

Is there a way to stop the display of C # metadata when navigating a class or method in a VB.NET project from a C # project

So the scenario is this:

I have a VB.NET project and a C # project in the same VS2010 solution. The VB.NET project references (and uses) the C # project as a reference to the project. If while I'm in a C # project and Ctrl-Click or Go to Definition on an element that is part of a VB project, it leads me to the metadata generated in C #, instead of the actual VB code file.

Is there a way to get this to go to the VB code file, so I don’t have to manually navigate in the browser / solution navigator?

+6
source share
2 answers

There is currently no way to get a "Definition Definition" for navigating between projects of different languages. The problem is not limited to C # and VB.Net, but extends to other managed languages, such as F # and C ++ / CLI. Each language treats the other as a reference to the DLL, and therefore you get metadata.

This is a known issue and something that language teams are well aware of. Usually it is in the list of potential elements for future versions of Visual Studio.

+3
source

Could you try (CTRL + comma), which is the "Go To" as a workaround?

+1
source

Source: https://habr.com/ru/post/905938/

More articles:


All Articles