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.

>>That was my undercover gig. You see, I circulated amongst y'all unknowingly and then reported the troublemakers and malcontents to the Developer Division Secret Police. They would take the carrot or stick approach - hmmm - do we send the "good cop" Ken Levy to iron out feathers or the "bad cop" - HE THAT HAS NO NAME - to make 'em disappear.
>>
>>Sure, I miss my firstborn child - wazzitz name - and my soul, but the branding was removed by cosmetic surgery so that worked out.
>>
>Haha, I guess I was a "bad egg" when I blew the cover on the VFP not being included in dot net thing. Everybody thought I had talked to some insider, when I just put two and two together. This was when MS had called the Feltmans and some others to Redmond to get them to put the word out. Oh well, they seemed to get over it.