>please don't patronize us in this way, by implying that we do not understand that which we are discussing. I have written applications in .NET (and a large number of other languages), I have briefly studied MSIL, and I have studied compiler theory in detail (and, in fact, written a couple), so I do believe I know quite well what I am talking about.
>
>What I think you do not understand, is the huge investment that many of us have made in VFP, and how important it is for us that this investment is respected by Microsoft.
>
>I don't care if you continue to upgrade VFP, or provide an upgrade wizard to VB.NET once the necessary mechanisms (like local cursor engine) exist in .NET or whatever, as long as you give us a viable path forward for our applications. (And please don't tell us to do a complete rewrite.)

I did not say everyone, I said some people. I do not think there will ever be a time where you can run your VFP code in .NET as-is without changes, so you should expect and plan for rewrite in .NET accordingly whether it is for VS .NET 2003 today, VS 2005 later this year, or future versions of VS/.NET. Obviously we will provide more and more information and resources for helping in this conversion/migration for those interested, but it is much like FoxPro 2.6 to VFP 3.0, even though @ SAY/GET is supported in VFP 3.0, you don't want your form and control inputs using them and you need to write new code and create new forms in the new platform.