>>VB.NET will continue to gain more and more VFP like features while C# probably won't.

I don't see this as an advantage. First off I can't foresee that the VB language would implement specific features in the language rather than using the framework to provide that functionality. If this MS' direction then it's shooting itself in the foot - if new functionality is introduced it should likely be implemented in the framework so that all languages can benefit from it. By putting stuff like that into one of hte languages, cross language benefits go out the window in a hurry.

This sounds to me like you have a stake in this. What's the story here? VFP team working on migrating developers using VFP to VB.NET via merging functionality?