Since using VB.NET I’ve noticed that, though VB.NET is supposedly a "first order" language in the Microsoft stable, there are a few things that make that facade seem fairly thin:
- Create a new project (File > New > Project) in Visual Studio (full installation) and you’ll notice that Visual C# is a root node element in the Project types tree where Visual Basic is buried under the "Other Languages" node.
- MSDN documentation for tasks as routine as sending an email will include sample code for C#, C++, and even J# while noticeably omitting a VB.NET sample.
- New language features of C# often take at least one point release of the framework to become available within VB.NET. Case in point: InternalsVisibleTo (now available).
I am sure the list is endless. These are just the top ones that stick in my mind at the moment.