The .NET functionality I referred to will involve COM interop. VFP will not have native access to the CLR.
>VFP.NET <g>
No, as disclosed already, this is not part of our plans. The Visual Studio and .NET language teams are now starting to work on adding many VFP features to future versions of VS/.NET. The VFP team is assisting in some of those efforts part-time. For related informnation on your comment here, see the VFP FAQ at
http://msdn.microsoft.com/vfoxpro/productinfo/faq/default.aspxQ: Is Visual FoxPro part of Visual Studio .NET?
A: No. Visual FoxPro 9.0 is a stand-alone database development tool which is compatible and evolutionary from previous versions of Visual FoxPro. Visual FoxPro 9.0 does not use or install the Windows .NET Framework. Visual FoxPro 9.0 is compatible with Visual Studio .NET 2003 in the area of XML Web services, XML support, VFP OLE DB provider, and more. Visual FoxPro 9.0 and Visual Studio .NET 2003 are complimentary tools that work great together, such as Visual FoxPro 9.0 plus ASP.NET for adding WebForm front ends and mobile device front ends to Visual FoxPro applications.
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.
