In prior releases, when in-proc Sx S did not exist, our runtime activation policy had to take into consideration the reality that only one runtime could ever be loaded into a process.
For self-contained managed applications the obvious choice was invariably the right one: activate the runtime that the application targets (derived either from metadata in the managed executable itself or from an application configuration file if one exists).
In such scenarios, the chosen policy has always been to activate in the latest installed runtime when no runtime has yet been loaded – a policy we call “bind to latest.” Consider the following example to help understand why this policy was chosen for managed COM class activation.
Let’s say that a native application X exposes an extensibility mechanism through COM, and two authors separately write managed extensions A and B that target .
NET Frameworks v1.1 and v2.0 respectively, and that application X and both extensions are installed on machine Z with both . Say that, in the course of normal execution, application X component B to fail, because the .