Tom Archer posts about MSDN preferring (or not) one language over another (link from Brian Loesgen):
http://blogs.msdn.com/tomarcher/archive/2005/11/21/495282.aspx

My thoughts (I posted similar comments on Tom's blog):
I definitely prefer C# for my daily programming over VB.NET. Actually, the unordered list of programming languages I prefer is:

However, the selection of programming language needs to fit the task at hand, and Eiffel and Spec# are not practical for most of my daily work. This has nothing to do with the quality of the languages -- I think Eiffel may be the perfect method and language for OO programming. However, I tend to be more productive in a team consulting environment for my current projects using Visual C#. However, after the revolution comes, you're all going to be using Eiffel. Or at least Spec#. So get ready.

I've used Visual Basic and Visual Basic.NET, and I've recently presented webcasts on Visual Basic.NET language features. I tend to think of Visual Basic the way I think of Escondido. It's alright and not completely unpleasant -- but I'm not going there unless someone needs me to be there.

As for examples, when I use C#, Spec# or Eiffel, I can express my examples better, there's less chance of error, and you're much more likely to get the content in a timely manner ;) So if you take into account marketplace realities and the relative audiences for all programming languages, you'll typically see my examples in C#.

The one issue I would raise is that there are language features in C# that do not map easily to VB, and I see many dual-code examples where the C# code is simply a literal translation of the VB. I've seen many C# examples that didn't employ the using(...){} syntax -- apparently because it didn't match the adjacent VB code (or maybe the author was more familiar with VB).  I would definitely prefer that examples in any language leverage the language rather than being presented in some weird common subset. Frankly, I'd be happy with examples in F# if it illustrated a better approach to solving the problem at hand.

And I'll try to add more Eiffel, Spec#, Scheme (and maybe Haskell) examples going forward.