>>
>BTW, the article is biased towards VB.NET (no surprise here). One of the most interesting reader's comment is from James. He mentions that being case-sensitive is an advantage of C# compared to VB.NET because IL (.NET Intermediate Language) IS case-sensitive too.
>>
>
>I think that is pure nonsense. VB and C# I believe, compile to the same IL. Perhaps C# is more efficient in some areas. Then again, I believe VB has JIT Compliation - which C# does not have - at least that is what I recall. I am sure somebody will set me straight.
>

Every .NET language has JIT compilation, even Fujitsu COBOL because they are all compiled to the IL before being JIT compiled.

>About 95% of what I do now is PL/SQL - which is a hybrid of sorts. It is not case sensitive - but you do have to deal with the semi-columns. Variable declarations in PL/SQL are just like C#: x int;
>
>Today, I probably would be fine coding C# - but I would miss the productivity of VB. In the end, I think it boils down to preference. And as of today, the emphasis is, or at least should be - on the framework.
>

From the productivity point of view, there shouldn't be any major difference. As you and Kevin Goff said it's the framework that really matters.

>
>>
>IMHO, VB.NET should only choosen by those who have only programmed in VB. All the others should choose C# as it is more integrated with .NET (it seems that a lot of .NET classes are programmed in C#).
>>
>
>I disagree - at least from a technical standpoint. Kevin McNeish some time ago, tried to make these arguments re: VB vs. C# - but they never held water. Now that .NET has been out for a while, I don't know if there are any cut and dry rules on the propensities developers will have. Certainly, people new to .NET who have VB experience, would gravitate to VB. But...that is not to say that those same people would not eventually go to C#. 80% of what you do in .NET is related to the framework. A string class in VB is the same string class you use in C#. And...ADO in VB is the same ADO in C# - so I don't see the big deal. Sure, there are differences. And...if and when those differences matter, people will make the right choice. But make no mistake, VB is no less integrated into .NET than C#.
>

Sure, the features differences between the 2 languages are not big, maybe a 5%. The only major difference I see is that C# can use pointers within blocks marked "unsafe". That shouldn't make any difference for business applications, but it's good to have this option when you need it. That's why a lot of commercial components are probably written in C#.