Unfortunately me, too.. :(

>Yes. I am skeptical about the claims being made by Mr. David.
>
>>Is that an irony? :)
>>
>>>Yes, exactly.
>>>
>>>>That's just like a dream.
>>>>
>>>>
>>>>
>>>>>Well the option to create native exe is not available in standard .NET. How we did this? We just take our .NET Assemblies (IL binary code as output by the VFPCompiler) and compiles them to Native, this is we don't do any conversion to C++. But I can tell you that the performance of the resulting exe is lot faster than the JIT (Net Interpreter) and really close to C++.
>>>>>
>>>>> With this capability you get the amazing productivity of VFP and the performance of C++, so for us it is the culmination of years wishing to build true natives from our VFP Code. And that will be the preferred way for us, as sellers of VFP coded products, to distribute our VFP apps to our customers, with that we get rid of the shortcoming in distribution of .NET.
>>>>>
>>>>>>>The native code generation will be just a switch in our Developer Studio that will generate instead of a .NET Assembly, just a true x86 / arm EXE or DLL or if you want and OBJ (linkable object).
>>>>>>
>>>>>>That's great news. I'm aware of .NET but if I understood true: "VFP Developer Studio can compile both true .EXE and .NET interpreter exe"? I didn't know there is an option for make true .EXE files with .NET. Are you convert applications to C++ and compile than or .NET supports native .EXE files too???