Navigating from VB.NET code to C# code problem -


There is a problem with the following situation:

Say you have a VS2008 solution , A console (console) application written in Vb.net, and a class library written in C #. The application references the classroom library project.

This is, of course, compliance and works well though, when you define the right-click function (in the vb.net application code) in the prototype / object type class library, and "Definition" Go to "Choose, the object browser opens to provide you with a list of available methods, class class library consists of poorly executed. However, if you try to do this, both applications and CL are in C #, it works just fine and you navigate through the appropriate functions / class smoothly. GOOD

A known issue? Solvable?

Did you try to add a project reference instead of the DLL reference? A project reference should be taken to the actual relevant code in the second assembly.


Comments

Popular posts from this blog

windows - Heroku throws SQLITE3 Read only exception -

lex - Building a lexical Analyzer in Java -

python - rename keys in a dictionary -