See Also: ApplicationActivator Members
There is a single designated instance of the System.Runtime.Hosting.ApplicationActivator class in each AppDomain to which all activation calls are routed. The AppDomainManager for the current AppDomain can provide its own custom System.Runtime.Hosting.ApplicationActivator for this purpose. If a custom System.Runtime.Hosting.ApplicationActivator is not provided, an instance of the default System.Runtime.Hosting.ApplicationActivator is created.
The following steps describe the behavior of the default erload:System.Runtime.Hosting.ApplicationActivator.CreateInstance method implementation:[The 'ordered' type of list has not been implemented in the ECMA stylesheet.]
A custom activator can tailor the activation of an add-in to a particular set of circumstances. For example, a custom activator could find an existing AppDomain to activate this add-in instead of creating a new domain every time.