>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?

VB .NET has more differences than just language over C#. There are things like IDE features, IntelliSense benefits over C#, etc. When VB .NET is compared to C#, it is not just the language that needs to be compared but the IDE. While they are both in the VS .NET shell, there are differences. C# is more geared towards code jocking C++ type developers, while VB .NET is more for RAD development. The .NET Framework is not the only features that will evolve. VB .NET will be the best RAD development tool for .NET development, as Alan Griver said in that video clip I showed of him in the keynote at EssentialFox. AS for your migrating question, that is simply not the case. Myself nor Microsoft as a company is trying to move or migrate VFP developers to .NET. Toledo is being developed and we expect most VFP developers to upgrade when it is released. Many VFP developers are either learning or plannig on using .NET either soon or eventually and I'm simply addressing those developers, it has nothing to do with VFP. Ideally VFP developers get MSDN Subscriptions and giving them VFP, VS6, VS .NET, many versions of Windows, and much more. I hope this clarifies thing here.