John,

One thing that strikes me: if you look at it from the right point of view, now with .NET, it seems that each language has become much less important versus the overall functionality granted by the CLR.

>>
>You say VB is more efficient? Is that just for you, or do you think it's more efficient, period?
><
>
>It is more efficient to me. I could never stand here and make a general prouncment that VB is more efficent or C# is more efficient. Apart from efficiency, I like the declarative nature of VB.
>
><<
>Personally, I like to use C#, and for me, now that I've gotten past the syntax part of it, I think I can do things faster in C# than the equivalent thing in VB.
><<
>
>I don't doubt that at all. It is a personal choice and for this reason, I believe the language is a secondary issue in .NET. I believe that C# AND VB are good languages for VFP developers to learn. IMO, to include one and not the other casts an implicit negative shadow on the omitted language. Perhaps in a few years, it won't be a big deal. But today, when EVERYBODY is learning, to simply make a prounouncement that essentially discards a language in my opinion, is a tad irresponsible. On one hand, I don't begrudge the choice of a language. OTOH, I do resent the implication that a choice was predicated on some alleged technical distinction.
>
>IMO, responsible vendors say something like "We chose C# because we prefer the language, but you can be equally productive in VB - the choice is yours."
>
>As for me, I am keeping an open mind. There will be times when I will simply force myself to use C#. Why? because in the effort, I will be a better .NET developer - which is what I see myself becoming. Expert .NET developers will know the framework inside and out first- which is independent of any language.