>VFP.NET (vfp language creating managed .NET code) is another issue and will probably never happen.

Yes, unfortunately you probably have reason.
I think there are some thing from .net that vfp should have and many others viceversa.
This strange situation where all the world is moving to .net except VFP (which is a MS product) can become a never-ending-story like the old question
"will MS continue develop new VFP version?"
which I hear since VFP3 days.