>VFP 3 did seem to get some attention from VB and C++ developers just by virtue of being in the VS suite. It was covered (some) in MSDN Magazine, included at Developer Days events, etc. By the same token, some of those same developers mistook the removal of VFP from VS as a sign that it was being dropped.
>
>All water long under the bridge now. I do think the people who argued against including VFP in .NET did so sincerely, believing it was the best course for the product.


I did the Nashville '98 DevDays presentation on VFP for MS and it was part of VS. It wasn't even the red headed stepchild, that was Microsoft's VJ++, which was so unstable, the guy doing the presentation was sure it would never happen.

We only got a passing glance from the vb group, even though I got lots of great comments on VFP.