Yes, and I'm saying the opposite is also necessary - moving .Net features into VFP.

Does this elevate the VFP team at Microsoft into a God-like status - everything our product does already should be put into .Net?

Where does this end...there will be no differentiation between VFP and .Net because the feature lists will be identical, so why bother continuing with VFP? Let's not put access to Longhorn technologies such as Avalon into VFP to teach that team a lesson?