In line comments.

>>IMO, many jump on the C# bandwagon because it has the letter "C" in it
>
>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.

This is probably the best reason for learning C#, you are learning Java syntax at the same time.

>
>The last point is C# has some more power features than VB.NET, mostly, being able to run unmanaged code.

I believe that C# and VB.NET have the same capabilities to run unmanaged code. After all, its the CLR the is running the code, not the language. I believe that C# can only emit managed code. You have to use C++.NET to emit unmanaged code. But I could be wrong on this point. Do you have any references?

>
>Because the differences are very trivial, I'd say its a completely personal decision based on what you already know.

A programmer approaching .NET has to learn the concepts first, then learn the syntax. The concepts will be the same for all .NET languages. In the end, its exactly that: a personal decision.


>Of course, when all is said in done, the real selling point will be if employers are specifically asking for C# or VB.NET developers as opposed to .NET developers (which is what I'm guessing Microsoft envisions).

Old biases persist. You can't really think of VB.NET as a second class .NET language. I personally was one of those who thought I would only learn C# and would bypass VB. Now I think differently. I will become proficient in both languages.

-Dave