That's pretty much how I feel about it too.  I started off in VB and I was pretty happy to go to C#.  For me the best thing about it is the similarities to Java/C++.  Any books or documentation written in Java/C++ can be easily reused for C#.  Java in particular has many books on architecture and patterns.  .NET is only starting to get those.  To be honest, for me I just don't see the point in using VB.NET.  It's nothing like the old VB.  That was one of the reasons I moved to C#.  Little to no experience or knowledge, other than the generic OO knowledge was reusable.  I ended up using Java and C++ documentation a lot the first few years .NET came out as there was nothing else.  At that point using VB.NET just added another layer of complexity for nothing.

This thread has some interesting comments: http://stackoverflow.com/questions/210187/usage-statistics-c-versus-vb-net

I find it funny (again, not surprising) that my preference is C# exactly because C/C++ is my background. :) As far as I'm concerned, (and it may have been mentioned) if you are working in .NET, then it's solely a matter of preference, since it 'compiles' down to the same language.

I pref C# because it's my background style, but I work in VB as well when a module I need to without hesitation, maybe just some badmouthing the lack of braces. I've modified some of the DNN core for Proof of Concept code; Modified some Onyak source code to do a few things differently, ect.

C# RULES! *runs away*

History.  DNN was originally developed as a VB project and hasn't been migrated.  No reason to, the beauty of the ASP.NET framework is that language doesn't matter.

Jeff