title: Intellisense in Visual Studio 2005 between C# and VB - can't navigate to definitions
body: <p>I'm absolutely stunned by the fact that MS just couldn't get it right to navigate to the definition of a method, when you're combining C# and VB projects in one solution.  If you're trying to navigate from VB to C#, it brings up the "Object Explorer", and if from C# to VB, it generates a metadata file.</p>
  
  <p>Honestly, what is so complicated about jumping between different languages, especially if they're supposedly using the same CLR?</p>
  
  <p>Does anyone know why this is, or if there's any workaround?
  Did they get it right in VS 2008?</p>
  
  <hr>
  
  <p>@Keith, I am afraid you may be right about your answer.  I am truly stunned that Microsoft screwed this up so badly.  Does anyone have any ideas for a workaround?</p>
  
  <hr>
  
  <p>@Mladen Mihajlovic - that's exactly the situation I'm describing.  Try it out yourself; project references don't make a shred of difference.</p>