>If we could have both, IOW, VFP continues along the same course it's been on since MS got their hands on it (from a technical standpoint) and we got VFP.NET which was a CLR version of VFP that just supported what the CLR can handle, then that would be interesting.

This would be my preference, but I guess it would come at a cost of other priorties for the Foxteam. Hmm...

>Unfortunately, if we got VFP.NET, I think development of regular VFP would stop just like it has for VB.

If the non .NET version of VFP would be so much more capable/powerful that a VFP.NET, do you think people would stop using the non .NET version of VFP?