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