Provides functionality similar to that of the ICorRuntimeHost interface provided in the .NET Framework version 1, with the following changes:
The addition of the SetHostControl method to set the host control interface.
The omission of some methods provided by
|ExecuteApplication Method||Used in manifest-based ClickOnce deployment scenarios to specify the application to be activated in a new domain.|
|ExecuteInAppDomain Method||Specifies the AppDomain in which to execute the specified managed code.|
|ExecuteInDefaultAppDomain Method||Invokes the specified method of the specified type in the specified assembly.|
|GetCLRControl Method||Gets an interface pointer of type ICLRControl that hosts can use to customize aspects of the common language runtime (CLR).|
|GetCurrentAppDomainId Method||Gets the numeric identifier of the AppDomain that is currently executing.|
|SetHostControl Method||Sets the host control interface. You must call
|Start Method||Initializes the CLR into a process.|
|Stop Method||Stops the execution of code by the runtime.|
|UnloadAppDomain Method||Unloads the AppDomain that corresponds to the specified numeric identifier.|
Starting with the .NET Framework 4, use the ICLRMetaHost interface to get a pointer to the ICLRRuntimeInfo interface, and then call the ICLRRuntimeInfo::GetInterface method to get a pointer to
ICLRRuntimeHost. In earlier versions of the .NET Framework, the host gets a pointer to an
ICLRRuntimeHost instance by calling CorBindToRuntimeEx or CorBindToCurrentRuntime. To provide implementations of any of the technologies provided in the .NET Framework version 2.0, you must use
ICLRRuntimeHost instead of
Platforms: See System Requirements.
Library: Included as a resource in MSCorEE.dll
.NET Framework Versions: Available since 2.0
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.