I hear ya when someone besides MSFT writes a component and you reference the component... that is what a component language is about. But I don't feel .net should go down the path of referencing another language runtime for every class that has common business functions that any language should have innately available. Put those common helper classes and enums into the system namespace exactly where the Math class is! (all .net languages should have them available in the system namespace - shouldn't have to reference another language). Think how pissed VB coders would be if MSFT removed the DateAndTime class from the vb.net runtime, but put it into the C# language only. Then every VB.NET program would have to reference the C# runtime and namespace in order to use it. Microsoft needs to create new FCL Financial and DateAndTime classes (using decimal instead of double where when dealing with currency) that are part of the core of the .net framework. No one wants to write all that crap over and over again. Sucks that I got to convert everything from decimal to double then back to decimal. Would love to get rid of all my VB wrapper methods!

Agree but there is no such thing as the C# versus the VB.NET runtime. There is only a Common Language Runtime. In which you can load assemblies with funny names as "Microsoft.VisualBasic". Which could be coded in something like cobol.net. Who knows ? Who cares ?

I am a C# guy. This is a matter of personal preference,  I know how to code with VB.NET but just...

I am a C# guy. This is a matter of personal preference,  I know how to code with VB.NET but just...