>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... :)
I don't think there's any kind of backward compatability issue here at all. The CLR is there to make native commands and functions of one language available to another, right? I don't think you're doing that in version 5 or 6, so there's nothing that will break. Everything you've used in the past is still going to be in the full VFP runtime, it just may not be in the CLR.
