I read the documents, it looks like it'll work as well as the FoxPro 2.x to VFP migration tools worked, which is another way of saying it doesn't look like it'll produce anything useful. The documents themselves make recommendations on programming practices in order to prepare for the migration. That's great for new VB6 projects, but doesn't help much with existing ones.

>> I wonder if anybody in the VFP community would be bold enough to do a similar thing - VFP6 to VS.Net?

VFP7 runs VFP6 applications unchanged. :-)

Now, as far as something that actually takes a VFP application and converts it to C# or VB.Net code goes, I don't think there would be much value in one. Sure, you could convert the forms to WinForms, but the code would be a different issue. It could be done, but the typical VFP application doesn't really fit the .NET architecture and changing all of the DML code to use ADO+ instead would be a big undertaking. It'd probably be just as easy to write a CLR compiler for VFP. ;-)