>>I am not talking about losing anything. With a compile time option to the CLR this will differentiate ourselves from VB. We then will be able write "full" VFP apps using the VFP runtime or write VFP apps that use a subset of VFP to conform to the CLR. Best of both worlds.
>
>Can you explain why we want that, if we've got already the option to write that sort of component in other languages ?? If VB/C# and others have at least as good OO implementation as VFP why write it in VFP and compile it to the CLR ?? What advantage does VFP.CLR have over the other CLR languages ??
>
>I can't think of any besides, we can use a VFP, xBase syntax to write thos apps.

This is one of the most convincing arguments against the CLR for VFP.