>>If I am right, surely the technical question is "how much of VFP's 6Mb runtime dll can go (and needs to go) in the CLR". If we are to use Winforms, I assume that much of the UI can go there. Maybe all of it.
>
>I really doubt that VFP will drop support for scx forms any time soon. And if we are to use WinForms, you can guarantee that we will lose local data access abilities in favor of COM access to data (ADO). Granted, for VFP data, this will be much nicer with a VFP OLEDB provider, but it's still quite a change.
>

I think all these questions have to do with the issue of backward compatibility. Will we be able to run VFP 5/6 exe under VFP 7? If CLR does not support all functions it means that existing applications will not work with it. This applies to other languages too, not only VFP. My assumption is that it has to support everything or it is no good. (Unless MS really wants us to rewrite all apps for CLR... :). I think it would be really stupid to strip out functions from the language in order to save 2 megs on runtime size. But that's my logic... :)