><snip>
>>... 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.
>
>Marc,
>
>This person is attempting to mislead you. There is no correlation between the IL being case-sensitive and the language being case-sensitive. Unless you are writing your own compiler, there will never be a reason to write IL code by hand.
>
>>
>>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#).
>
>This is misleading also. There is no relationship between the language that the framework classes were written in and the language you use to write code. You will never see or work with the source code of the .NET framework and the interface of the framework classes is identical, no matter which language you are using.
>
>With the information that Microsoft has released about the next version of .NET, it is clear that VB.NET is being steered towards maximum productivity and C# is leaning towards raw power. The beauty of .NET is that you don't have to permanently choose one language over the other. Work with both of them, see which one that you like the best. Then use that language for most of your projects.

Marc, I religiously stay out of these type of threads but this is the absolute best answer I have ever heard. 'I' (as if 'I' mattered [wink]) use both. I have found that you don't have to choose. You can use all of VS together as it best suits 'your' needs. The best language will always be relative to experience with a language and personal preference. Keith, great job.