I am in general agreement that VFP should not be in the VS box but I can see some disadvantages:
Convincing clients that two development tools are needed and not just one if pushing a VS and VFP combined application.
Wouldn't it make it harder for the Fox Team to get the internal cooperation and resources to make VFP work and play well with others?
And some advantages not yet (AFAIK) discussed:
MS could promote VFP as the homogenous 1- and 2-tier tool, thereby (finally) identifying a real niche for VFP and allowing MS to draw a clear line between desktop tools and .Net tools. This may be good for all concerned.
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05
