>>Ask yourself why VFP is unique. It is about the local data engine and the way the VFP language is tightly bound to the data engine - neither of which exist on the .NET platform at this time.
>
>
>Ken. You're just adding fuel to the fire by ending your thought with an open ended phrase ("...at this time"). :)

Ads fuel to what fire? I don't see the issue here. Refer to the VFP FAQ at http://msdn.microsoft.com/vfoxpro/productinfo/faq/default.aspx:

Q: What is Microsoft's position on Visual FoxPro related to Visual Studio and .NET?
A: We do not have plans to merge Visual FoxPro into Visual Studio and .NET, and there are no plans to create any sort of new Visual FoxPro .NET language. Instead, we are working on adding many of the great features found in Visual FoxPro into upcoming versions of Visual Studio, just like we've added great Visual Studio features into Visual FoxPro. If you want to do .NET programming, you should choose a .NET language with Visual Studio.