>When you say "some" in an open discussion like this, you are effectively accusing everyone. If you are to make a claim that someone do not know what they are talking about, you should have the guts to address that person directly. However, I don't think we need to discuss this any further.

Some means some, all means all. You can interpret that incorrectly if you want, unfortunately.

>The point here is, that it is still _supported_, and the application can take advantage of the new features without a complete rewrite. If you provide a similar story with VS.NET/2005/2007(?) (i.e. much better interop than what exists today), it would be great.
>
>If not, I guess our application will just stay in fox for another 5-10 years or so, and when we do rewrite, .NET will probably be obsolete as well, and we will at least save one rewrite (.NET --> TheNextBigThing).

It is not just about code (commands and functions), it is about architecture and logic. If you want to run VFP applications as-is, you will need to run them on the VFP runtime as you do today. If you want to run code on the .NET runtime, you will need to use .NET code that is also properly architected and executed to properly implement the application.