Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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.
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