>Your disagreement seems more politically driven. You even admit the fact that you are the lead program manager on the VB.NYET team. I wonder what your answer would've been had you been the lead on the C# Team.

That's why Czarina is correct that MS should consider hiring C# evangelist. It's really disappointing that some MS people are giving advice in favor of another tool, which I feel it should not be.

If our basis is "EASIER LEARNING CURVE" in choosing one from an array of .Net languages, we might end up with VB. But judging from what the technology dictates plus the pace of it, we need flexibility long term. And so we choose C# because (and I've said these before in other thread but for purposes of answering the original thread):

1. C# it's Java like – shifting to Java if needed is no longer an issue.
2. C# ECMA standard - which means that others can have a go at creating C# compilers and variants for platforms other than Windows. And so we'll see different compilers appearing on other platforms thus increasing its user base.
3. C#, most of the time it has shorter syntax than VB.
4. C# is planned to be relied upon by MS as the language of future software development.
5. C# has higher profile than other .Net languages.
6. C# is touted as the language of the .Net platform.

I've talked to a lot of VFP developers here and 7 out of 10 choose C# because of the above reasons.

Thanks and congrats for being candid regardless of who you are talking to.