>Creating a VFP COM middle-tier component in the VS IDE does not indicate anything about CLR involvement.

Strictly speaking, that is true enough David. I'm just thinking it would still be ...well 'goofy' for MS to promote VS .NET as a development IDE, hype the CLR concept and then add a caveat of "all participate in CLR! er..uh, well except for this one product. Yes, yes it is *our* product but and while it meets the ECMA compliance requirement and you may debug in and out of it, whether as a COM or not, and package it up nicely with the VS Installer, you won't have it in CLR until some other day, cause...uh...I..uh..." The VS .Net IDE and CLR should at least include all VS products right out of the gate to appear congruent. "Hey, here's our new horse. You should bet on it. And we'll get that missing leg attached someday really soon. Trust us."

Steven-