Denis, having a separate framework for each version prevent that installing the latest version break old application based on the old framework (remember DLL hell?) Of course MS could release a newer version of the framework that is 100% compatible with the older version, but we all know that only good in theory. Practice showed us that even if a component is labeled 100% backward compatible, it's really isn't. I must admit that the VFP team did a wonderful job on this, but the VFP runtime is far as complex as the .NET framework.

Beside, having a separate framework for each version has it's advantage other that DLL hell resolution. You are no longer tied to old code. This mean that if you mark a function as obsolete in version N of the framework, you can take it of completly of the framework in, let say, version N + 3 of the framework. This lead to a simpler and lighter framework. How much leaner the VFP runtime would be if it woudn't have to support old commands like @...SAY?

>I can't believe that they (MS) did'nt think about that. No escuses for that. There should be just one framework installed.