I like to say that the only reason BASIC is still popular is that it was Microsoft's first product, and they've be shoving it down our throats for the past 35 years. It should have died a long time ago.

With that said, I've worked on two sizable .NET projects and both were done with VB.Net - though there was a bit of C# because either the translation was a bitch, or the construct didn't exist in VB.Net. The only advantage I see with VB.Net is that the Visual Studio editor is much more friendly to it (in my experience anyway) than it is with C# - Intellisense seems better, and so does autoformatting (note that since I have not used C# as much, I may just be missing something in the configuration of the IDE...)

A major disadvantage in VB.Net is that they brought in a lot of VB6-era crap way back in .NET 1.x to ease the conversion of VB6 code. That stuff is still in there, and VB6 coders are coding new code using those... "extensions" rather than using the more neutral .NET classes/methods/whatever. I don't know how many times I asked my boss why he still used that crap. "But... It works..." Right. Hey, I like to bitch.

While looking for help on the web, I found the vast majority of solutions were in C# - check out the MSDN forums, various blogs, etc... Books have a tendency to focus on C#, and if there is a VB version, it usually comes in months later (e.g. Pro LINQ.... from Apress.)

Many languages share the C ancestry, which makes switching between C, C++, C#, Java, PHP and a few others much easier. PHP is a bit of a stretch here, but it does have a lot of C-like constructs. VB? Well, it's pretty much its own little thing and that's that.

A project leader in my organization recently told me that more and more new projects are being developed using C# instead of VB - FINALLY. When .NET was introduced in our organization, they more-or-less-officially went with VB.Net because of all the VB6 coding that was already going on. The powers that be later admitted to me that that wasn't their best move.

As somebody else above pointed out, I wouldn't say no to a VB.Net project, but I'm still hoping that it will be slowly eradicated from newer development at my place of work.