I've been working with .NET for 2 years now, and I agree with John 100%.
Somewhere in this thread, someone asserted that C# was somehow more 'integrated' with the .NET framework classes than VB.NET was.
While I can't quote every piece of detailed syntax available for, say, ADO.NET, I really don't think there's much of anything in ADO.NET that is more accessible from one language versus another. (or if there is, I'm not aware of it).
The entire concept of the framework is based on language-independence. (Has always been my understanding). So I'm curious about specifics to support the assertion that one language is more 'tied' to the framework.
I worked in C for years and never worked much with VB - so naturally I gravitated towards C#. But many were the reverse. So in many ways, the language choice is largely preference and comfort level. And truthfully, as I look back on where my learning curves were, the language itself represented a small part of it.
I'll mention something I said earlier on this thread - several experienced developers are using VB.NET for user interface work and C# for the non-visual, application-tier work. This may turn out provident, based on what's been discussed for future language enhancements.
But the mantra should be "the framework, the framework, the framework". I don't think that can be stressed enough.
Kevin