Plinio,

I'm not sure I understood you at first, and maybe I still don't, but perhaps you'd agree. It seems to me that there isn't much debate about the technical decision to keep VFP out of the CLR, but the real issue is pure marketing. We've all heard about the great ways that VFP 7 can produce and consume web services and somehow fit in well with .NET. So why not just call it VFP .NET and be done with it? In or out of the VS box, with or without the CLR, just please, let VFP look like something that fits in, because it does. It wouldn't take a lot to change people's perception if the tiniest fraction of Microsoft's marketing power were intelligently channeled toward VFP.

Mike

>Excuse me the "anwer" instead of "answer". Poooorrrr English spoken.
>
>Ok, Do you thing it's possible?
>Could We have a VFP .NET out CRL?
>Could We have more presence on MSDN Magazine, MSDN Newsletters, MS Home Page, etc?
>
>Are there impossible wishes?
>
>We know you're making a good job, Is there anybody at Microsoft with You?
>
>
>
>>But in all, a very interesting, useful, and educational thread. I know many people have been following it, including myself and others on the Fox team. I haven't posted any specific comments or questions on this thread, mainly because it has evolved well and I don't really have to. Thanks to you for starting a thread on this topic and others on it, one of the more interesting UT threads in a while.