Becuase VFP is a Development environment, if the MS marketing guys called it "VFP.NET" the people expect that the product fit rigth in it... And this is not the case. Obviuos is possible connect it...but also is possible with PHP, C, and thats...

VFP can be called "VFP.NET" if this LANGUAGE can produce .NET code. If can consume .NET clases. If other .NEt LANGUAGES can inherit from VFp .NET clases, if you can VFP.ASP.NET, and thing like this..if not, in the best place "VFP can Connect to .NET"...

Probably, call VFP.NET can cause more damage to VFP if this is not a real .NET language.