>>You almost have my point nailed down. I qualified the statement with the word "materially". I said that in material respects, VB .NET is not technically inferior to C#.
>
>I'm not sure what you mean by "materially", care to explain?

A hypo to illustrate:

If you have a business with 10,000,000 in revenue, and investment choice that would either make 1,000 or lose 1,000 would not be material as far as the performance of your business is concerned. A decision that could lose 100,000 OTOH or perhaps 1,000,000 would be material.

Another one..

Whether VFP is or is not in MSDN does not have a material impact on how many people subscribe to MSDN...


>
>I still disagree that they are on equal ground, C# definitaly has the upper hand for reasons we've already gotten into, but like I've mentioned elsewhere in this forum, the argument that C# was written for the .NET Framework while VB.NET was adapted to it hardly makes a difference.
<

As an absolute, I have never said that VB and C# are on equal ground. In material respects, as far as the type of applications I develop, I think they are on equal ground. And having said that, I would opt for VB. Your opinion may be different and that is A-OK.

FWIW, I think we agree that the issue of C# being written specifically for .NET does not make a difference...