>>Sure, it's only catering to perception (as the wiki article suggests) - but our economy is BASED upon perception. Heck, our very EXISTANCE is based upon perception!
>
>Around here we have a saying that "Perception is reality" because most people will never check the facts. In other cases, their "perception" is actually making things fit their desired goal and they make you prove the opposite. I've had these types of discussion with numerous folks about Fox (including MS folks).
>
I think it is agreed that perception is important and is an ongoing problem with VFP. The question is what effect would removing VFP from VS.NET have on this perception? It could go either way, but I believe this is largely dependent on marketing. Leaving it in would seem to give the perception that VFP continues to be part of Microsoft's strategy. On the other hand, it could also invite reviewers to bash VFP for having little in common with the other tools and not utilizing the .NET framework, CLR, etc. As a separate product, VFP could potentially be marketed for all of it's strenghts, from desktop to enterprise. At this point, it is unknown if that would actually happen.

BTW, I'm still undecided. Where's Whil when you need him? <g>.