>I don't even think they need 98% compatibility - they could have a really nice niche market assuming they ever get to the point where you could get almost any older VFP application into .NET in anything less than a month of redevelopment time; so even 85% compatibility might be OK (assuming it was the right 85%). That would be a big win for a lot of shops who have invested a huge amount of time into their product (where a full rewrite just isn't possible). All the legacy stuff ends up in one project of your solution, and all the new development can go in other projects. I'm excited by the possibility, but I still have a lot of doubts as to whether they'll get there or not. It's not a matter of talent or ability - they've proven they have the technical chops to pull it off. It's a matter of focusing their efforts more and tackling some of the less interesting aspects of this.

I think so even %98 is a problem. We want VFP .NET compiler. Because we just want to move our current VFP projects to .NET easly. If compatible will %85 maybe move to C# would be a better solution.