Huh? I'm used to C# and VB.Net on MSVS 2008. There really isn't that much difference between the two. There are only a few things you can do in C# that you can't do in VB.NET, but so far they haven't hindered my development efforts in VB.NET
One thing I will say against VB is that right now you have to be more careful with its loose typing. As a programmer I have to be more disciplined. There is nothing like a strongly typed language like C# (or even worse Ada) to keep your coding honest!
In fact, I think when building an UI, VB is better because hooking up the event handling is a little more forgiving than in C#. And in VB.NET its eaiser to manage the namespaces ...
In any event, I think Visual Studio allows you to mix and match in the same solution anyway; so why not develop user interfaces in VB and backend processing in C# if you really have to? If your following your OOP principles properly, you ought to be separating out your presentation anyway.
It seems there are certainly more jobs available in C#, so right now I would advise anyone new to the industry to concentrate on becoming proficient with C#; the switch from C# to VB.NET should then be trivial.
There is nothing worse for a programmer's career than to be stuck in a niche language, so really I'm surprised that people get so hung up on their favourite language. After all most modern languages all offer the same features: modules/functions, variables, if statements, loops etc.
Speaking as a professional programmer of over 21 years, code is just code. Its all the same regardless of the language because the really important part is how the problem is solved.