>MSFT is moving to a managed code world. Other companies and products (Avalon, SQL Server, Oracle, DB2, Fujitsu, Borland, Activestate) are on board with the .NET platform. VFP simply doesn't fit into the managed code world. VFP COM objects can't be debugged from external apps. The .NET debugger allows you to step through T-SQL stored procedures, Managed Code, C++ code, etc. .NET supports remoting using managed code.

While I agree with you that is all about the platform, there are things we can and will do for enhancing VFP to interop more and more with the .NET platform. In fact, our plans for enhancing VFP for .NET interop is our primary goal for enhancing VFP going forward. We will also enhancing functionality for VFP reports, productivity, and other that have nothing to do with .NET. The goal is not to have VFP be able to build a .NET (managed code) application since VFP will remain Win32 based. But our main goal is to have VFP leverage as much as possible integrated into the .NET platform.