>>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 just use C# huh? I mean that's how I'm supposed to battle the lack of marketing by MS and misconceptions for VFP when it comes to dealing with my current and potential clients? Hey it doesn't bother me any - I mean by the time all this *functionality* is added into C# and VB.NET as you're implying, then there will be no more new VFP's anyway because it won't be needed.

And how irrelevant is it? What you're suggesting is that it's easier to market this odd-ball step-child that's aparenlty outside of the big 'push' that MS has going than it is to simply make it part of it. Hey if you can't beat em, join em right?

I'm suprised you answered my question the way you did, as it sorta sounds like one more nail in the coffin.