Navigating from VB.NET code to C# code problem

There seemes to be a 开发者_运维知识库consistent problem with the following situation:

Say you have a VS2008 solution, consisting of a (say console) application written in vb.net, and a class library written in c#. The application references the class library project.

This, of course, complies and works well. However, when you right-click (in the vb.net application code) a function prototype/object type defined in the class library, and select "Go to definition", the object browser opens providing you with the the list of methods available for the class the class library consists of. BAD. However, if you try to do the same when both the application and cl are in c#, this works just fine and you navigate driectly to the relevant function/class.GOOD.

Known issue? Solvable?

Did you try adding a project reference instead of a DLL reference? A project reference should take you to the actual relevant code in the other assembly.

It's a known issue, the workaround are two: use ctrl+, or use some plugin that add this function, like resharper.