>That is a intelligible explanation. Why didn't you say that before? Only you said like that "We have not any plan to move VFP to .NET."
>
>However you can put a alternative compiler for creating .NET compatible .EXE files like delphi's did, can't you?

But why do that when you can get the same functionality with VB .NET, or C#? Think about the confusions people have today dealing with selecting or using both those languages. Now throw in a third that doesn't really look like it use to (without the data stuff) and now you have three to use and learn, document with samples, etc. The right way to do this is to add VFP like features to the VB and C# languages, as well as the .NET Framework classes.