01:53
Unknown
.NET CLR exposes interfaces by which an external host can control the way .NET run time runs.
In previous versions of .NET it was done via COM interface "ICorRuntimeHost". In pervious version you can only do the following with the COM interface.
=> Specify that whether its server or workstation DLL.
=> Specify version of the CLR (e.g. version 1.1 or 2.0)
=> Specify garbage collection behavior.
=> Specify whether or not jitted code may be shared across AppDomains. In .NET 2.0 it's done by "ICLRRuntimeHost".
But in .NET 2.0 you can do much above what was provided by the previous COM interface.
=> Exceptional conditions
=> Code loading
=> Class loading
=> Security particulars
=> Resource allocation
SQL Server uses the "ICLRRuntimeHost" to control .NET run-time as the flexibility provided by this interface is far beyond what is given by the previous .NET version, and that's what exactly SQL Server needs, a full control of the .NET run time.
In previous versions of .NET it was done via COM interface "ICorRuntimeHost". In pervious version you can only do the following with the COM interface.
=> Specify that whether its server or workstation DLL.
=> Specify version of the CLR (e.g. version 1.1 or 2.0)
=> Specify garbage collection behavior.
=> Specify whether or not jitted code may be shared across AppDomains. In .NET 2.0 it's done by "ICLRRuntimeHost".
But in .NET 2.0 you can do much above what was provided by the previous COM interface.
=> Exceptional conditions
=> Code loading
=> Class loading
=> Security particulars
=> Resource allocation
SQL Server uses the "ICLRRuntimeHost" to control .NET run-time as the flexibility provided by this interface is far beyond what is given by the previous .NET version, and that's what exactly SQL Server needs, a full control of the .NET run time.
0 comments:
Post a Comment