Following up an old thread here, because of new relevance

>>Two major ones, not getting into technical differences like Kevin, would be the available documentation/resources and the fact that C# is an open standard. Meaning that the time I invest into learning C# should be eased by the resources and I could port code to other platforms using the C# standard.
>I see these as perceived benefits of C# and perceived weaknesses of VB .NET.
>A benefit not taken advantage of provide zero value...

This wasn't perceived at all:
http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/002/097/msdncompositedoc.xml

The Common Language Infrastructure (CLI) is the ECMA standard that describes the core of the .NET Framework world. The Shared Source CLI is a compressed archive of the source code to a working implementation of the ECMA CLI and the ECMA C# language specification.

This implementation builds and runs on Windows XP, the FreeBSD operating system, and Mac OS X 10.2. It is released under a shared source initiative. Please see the accompanying license.

It also adds:

The Shared Source CLI archive contains the following technologies in source code form:
Compilers that work with the Shared Source CLI for C# (ECMA-334) and JScript.

I very well could be wrong, but it appears as if VB.NET code will not be immediately compilable to OSX and BSD but C# code is.