>I did not say everyone, I said some people.

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.

> 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.

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).

Eyvind.