>>Which would be easier to market, Visual Foxpro or Visual Foxpro.NET ???
>>
>>Which would attract more users? Visual Foxpro or Visual Foxpro.NET ???
>>
>>Which would be easier to sell as a development tool to a developer's clients? Visual Foxpro or Visual Foxpro.NET ???
>>
>>Which would be more 'in-line' with what Microsoft is doing towards there software development tools? Visual Foxpro or Visual Foxpro.NET ???
>
>These are irrelevant questions since the issue is that it would all be harder to market yet another .NET language and take away resources of both VB and C# instead of adding better data functionality to both VB and C# that gives you more and more what VFP does today.

So if I understand correctly MS developed a set of tools (.Net) based on two languages that don't really have data functionality and now you're adding data functionality to it.

Would'nt it have been easier to start with VFP, which already have data functionality and build .Net around it?

I don't know just an idea I'm throwing...