>>>
>>>Some people I respect argued that VFP should not be part of .NET. Their argument won out. In retrospect I consider the developer-driven decision to bail out of VS to be the fatally wrong decision.
>>
>>I never understood the rational behind people wanting VFP to be just a standalone tool.
>>
>>If it was the flagship tool of a company (other than Microsoft) that would obviously make sense, but when Microsoft is pushing EVERYONE to Visual Studio, why not keep VFP in it?
>>
>>Makes no difference now, though.
>
>If I recall correctly, it was to give the Fox Group at MS more freedom to do whatever....

Freedom wound up being freedom to find new employment.. :(