>Regardless...it is a bit of an over-reach to couch the reasoning in the way you did. FWIW, I don't really care, I simply wanted to correct the record here. I think the reasons were more technical than an appeal from the community. Also, there were two sets of issues. The first was whether the ENTIRE product should go to the CLR. The second was the issue of creating VFP middle-tier components in VS .NET.
>
>With regard to the first issue, that was universally rejected as being a good way to go. As for the second issue, I was sorry to see that not happen. Then gain, COM is not part of the VS .NET story, so with that in mind, I can see why it was no longer included. FWIW, the component debugging feature never worked correctly anyway...
RIght, it didn't. I chalked it up to beta 1 and figured they would get it working by Beta 2. FWIW, I'd like to see this feature in Toledo.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer