>VFP is going to re-appear as VFP for NET or through VB.Net
>It makes business sense.
>MS cannot expect hundreds of thousands of mainstream developers to pick up Visual Studio C# with thousands of classes and properties.
>Remember, VFP is basically an aggregation of C++ routines.
>ETechnologia and others have detected this niche and are vigorously pursuing it.

I don't see Microsoft trying to steer hundreds of thousands of mainstream developers to VFP. They never tried to steer the thousands of VFP developers to VFP - they only steered them away.

Microsoft is done with VFP.

If eTechnologia succeeds with a .NET port, more power to them and I'd be interested in it.