I think MS won't name it VFP for .Net till they can back up this claim. As MS is the iventor of this term, that would make their job a little easier.

I think from a marketing view point, choosing this name can be a win win situation for VFP and hopefully that will bring MS to market VFP more agressively. Before .Net, there was no advantage of VB over VFP as far as capabilities, I'd even go further to say that VFP excelled over VB in many respects but the marketing muscle of MS made VB what it is today as a lot of 3 party products such as Crystal Reports and a lot of slick ActiveX were introduced to the market fully tested for VB but bug ridden when used in VFP adding further to the imbalance.

A pet peeve for VFP community was MS doesn't back it up as strongly as it should, adding '.net' would entitle more backing by MS to VFP.

How does that sound?