I am talking about marketing to the whole computer industry and not just the VFP community. I guess I won't hold my breath.

>What are you talking about? All I said was that
>1) it was discussed here before, i.e. can search for the earlier discussion,
>2) There may be FoxPro Advisor articles about it, (which Nick directed you to with direct links) and
>3) gave you a direct link to the MS VFP website where one of the reasons were noted?
>
>
>Pardon me for trying to be of some assistance...
>
>- Brian
>
>
>I know why doesn't mean everyone knows why.
>>
>
>>>I am curious to know if MSFT has/will have to tell the world why VFP is not in Visual Studio.NET. Have there been any press releases? Or is it our job to defend every time someone says that VFP is MIA because it is not part of Visual Studio any more?
>>>
>>>
>>>Ken, as well as many others here, have mentioned the reasons why. I think he reiterated the reasons in a FoxPro Advisor article as well. You can see the main reason of "it's not a .NET language" at the MS VFP website:
>>>
>>>http://msdn.microsoft.com/vfoxpro/prodinfo/qa.asp
>>>
>>>
>>>
>>>- Brian