A lot of things: books, websites, 3rd party tools, etc. have more support for C# than VB.NET. It think it's assumed that more people use C#, but I'm not sure that's true - not if all the millions of classic VB programmers upgraded to VB.NET it wouldn't
be anyway. But Microsoft has promoted C# as the 'serious' .NET language, so the perception is out there that supporting C# is a must and that VB.NET is a bonus.
At work I write ASP.NET and Webservices most of the time and the company uses VB.NET for all it's .NET projects. I hadn't used VB.NET before I joined them (although I had used VB6 for many years), but I was a user of C# for several years and convinced them
to hire me based on how much transferable knowlege there is between the two as well as my classic VB experience.
Anyway, my observation is that VB.NET is pretty-much perfect for the work we do. Mostly due to one feaure: the compiler generates code such that in comparisons operations, the empty string is equal to null (Nothing in VB.NET). That saves *so* much redundant
typing that you have to put in by hand when you write in C#. OK, there are other benefits to VB.NET and there are also some downsides, but certainly anything you can write in C# can also be written in VB.NET.