>>There were really good reasons to get VFP out of .Net. We were prisoner to their long, long product cycle and had to wait for their builds as I understand it (the decision was made a couple of months before I started).
>>
>>Also, the direction VS was (is) going and VFP was going were a lot different and I think it would have been a disservice to VFP developers to live with the transition and dissimilarities.
>>
>>Just my opinion.
>>
>
>True, VS is still around and VFP is dying a slow death. They obviously went different directions....

Possibly would have died even a faster death within .Net Part of the attempt was to establish a separate identity for VFP. C'mon, no one had a clear picture of VFPs role, strategically, with VS 6.