VS.Net multi language bug - 2.5 years and still going strong?
This is indeed a very annoying bug, and arguably has high importance because being able to develop on multiple languages is one of VS.Net's most touted features. Annoyingly enough, this problem only happens when the Unifying GUI app is a VB.Net app, not C# one.
Does anyone from the VB.Net\VS.net team care to comment on why this problem, that has existed ever since the Beta 2(or beta 1) days of VS.Net has not been fixed up until today, and
still exists in Whidbey?
[via
Philip]