"Clearly career-wise C# is the way to go..... most serious developers despise the bizarre and legacy-ridden basic syntax so there will be a hard push to use C#. There is much to be said for a clean slate. Also worth noting, Microsoft is standardizing on C#....must be a reason there."
This brings up a point I have rarely seen discussed. Regardless of the endless language "features" debate, C# has become the defacto standard for .NET development. If anything, .NET developers should really get to know C# for that reason alone--even if they think VB is still the greatest thing since the Apple IIe. Case and point:
SourceForge doesn't even projects to be classified as VB.NET currently. They must be mashed in with the "Visual Basic" group:
As long as you never have to modify or inspect anyone else's .NET code, it may be fine to ignore C# for the time being, but chances are that isn't going to be the case for very long if you want to take advantage of the rapidly growing .NET community's resources.