>In addition to David, To me it's like we can do all the things we can do in VB we can do with C++. On only some points (features that closely related to the CLR) we have to use some workarrounds. As said before, the whole .NET things is much more than only CLR. VFP can fully participate in .NET excluding compiling to the CLR. AFIAK, this only a small part of the whole, which can be (easely ??) bypassed.
>

That's interesting; I take it you know more than the MS people about this. As of last week, the MS team indicated that VFP will not be a full participant in the managed code playground. While from an application programmer POV it may not matter, there are fundamental differences between languages that emit IL via a JIT compiler, and VFP's interpretive environment. There will be circumstances that will rule out VFP as the principal tool for developing certain types of apps. VFP still won't be able to publish an entrypoint for callbacks from what I've seen and read (the only significant change in the DECLARE...DLL appears to be the new OBJECT datatype, which can be used to return an interface (a pointer to a pointer to a dispatch table) which can be used to return a COM interface to VFP in a form VFP can use - Calvin demonstrated this and went into some detail regarding the IAccessible interface in his session on Active Accessibility; some of this is from playing with a pre-beta release that's buggy and the MS team stated will undergo some major changes before it ships IAC, and some of it is from reading. It's serendipitous that I'm taking a theory of formal languages course this term; a lot of the theory fills lots of gaping holes.

>So we are debating only a small part of .NET where we cannot have direct support but might have via COM services etc..
>

No, people are speculating wildly and pointlessly on this, in spite of being told the product is a couple of months from entering beta, perhaps a year from a real product, and a new OS in there as well. It makes much more sense to play with the Tech Previews, both VFP and the PDC release, and keep on top of the MS site. Even the development team at MS isn't sure where things are going; perhaps a little empirical observation and waiting is in order.