VS2010: Going to definition for a C# member in a VB.NET project (and vice versa)

Question

I have a solution with a C# project and a VB.NET project. The VB.NET project references the C# project. When I am in the VB.NET project and want to go to definition of an object member located in the C# project, VS takes me to the object browser instead of the member. The same occurs when I am doing the opposite in the C# project. What I would like it to do is expose its member to me.

Note: I am referencing the actual project and not the DLL.

They hide it well, but sometimes it peeks through the cracks that the VB.NET and the C# IDE are completely different chunks of code. — Hans Passant, Dec 20 '11 at 20:14

score 2 · Accepted Answer · answered Dec 20 '11 at 20:11

2

This is a known limitation of Visual Studio. The corresponding Connect issue was closed as "By Design": http://connect.microsoft.com/VisualStudio/feedback/details/349633/go-to-definition-goes-to-object-browser-when-type-is-written-in-c-and-current-code-is-vb

answered Dec 20 '11 at 20:11

bobbymcr

23,769
3
56
67

Well that sahks. Thanks for the link. Now I know! – oscilatingcretin Dec 20 '11 at 20:29

VS2010: Going to definition for a C# member in a VB.NET project (and vice versa)

1 Answers1