D

database servers, extensibility of, CLR Hosts and Other Extensible Applications

debugging manager, CLR Hosting Managers, Loading Code Domain Neutral

defined, CLR Hosting Managers

purpose of, Loading Code Domain Neutral

default application domains, Statics for Domain-Neutral Assemblies, Step 3: Call AppDomainManager.InitializeNewDomain

default CLR host, The CLR Startup Shim, The CLR Startup Shim, The CLR Startup Shim, Using the Default CLR Host, Using the Default CLR Host, Using the Default CLR Host, Using the Default CLR Host, Using the Default CLR Host, Using the Default CLR Host, Using the Default CLR Host, Invoking the Default Host: Running Managed Executables, Invoking the Default Host: Activating Managed Types Through COM Interop, Defaults for the CLR Startup Options, Defaults for the CLR Startup Options, Defaults for the CLR Startup Options, Defaults for the CLR Startup Options, Defaults for the CLR Startup Options, Defaults for the CLR Startup Options, Running Managed Executables, Upgrades, Customizing the Default Host Using Configuration Files, Concurrent Garbage Collection, Version, Version, The <requiredRuntime> Element and .NET Framework 1.0, The <requiredRuntime> Element and .NET Framework 1.0, Turning Off ApplicationBase Searching

advantages of, Using the Default CLR Host

bindingRedirect element, The <requiredRuntime> Element and .NET Framework 1.0

build type configuration, Defaults for the CLR Startup Options, Concurrent Garbage Collection

COM Descriptor Directory, Invoking the Default Host: Running Managed Executables

COM interoperability, Invoking the Default Host: Activating Managed Types Through COM Interop, Upgrades

configuration files for., Turning Off ApplicationBase Searching (see )

default startup options, Defaults for the CLR Startup Options

defined, Using the Default CLR Host

domain-neutral code default, Defaults for the CLR Startup Options

garbage collection configuration, Defaults for the CLR Startup Options, Customizing the Default Host Using Configuration Files

invocation methods, Using the Default CLR Host

managed executables, running from, Using the Default CLR Host

managed executables, version selection, Defaults for the CLR Startup Options

OS version issues, Using the Default CLR Host

Portable Executable (PE) headers, Using the Default CLR Host

requiredRuntime element, The <requiredRuntime> Element and .NET Framework 1.0

startup shims with, The CLR Startup Shim, The CLR Startup Shim

supportedRuntime element, Version

upgraded CLR versions, The CLR Startup Shim

upgrades with managed executables, Running Managed Executables

version configuration, Version

version selection, Defaults for the CLR Startup Options

_CorExeMain function, Using the Default CLR Host

demands, CAS, Permissions

deployment, Application Domain Configuration Settings, Customizing How Assemblies Are Loaded, The AssemblyBindInfo Structure

cocoon model., The AssemblyBindInfo Structure (see )

default assembly loading scenario limitations, Customizing How Assemblies Are Loaded

directory settings for assemblies in application domains, Application Domain Configuration Settings

disabling the CLR, The CLR and Process Lifetime, Failure Escalation

DisallowBindingRedirects property, Assembly Binding Settings

DisallowCodeDownload property, DynamicBase

DisallowPublisher property, Assembly Binding Settings

discovery of hosting managers, Other Unmanaged Functions on mscoree.dll

DLL hell, avoiding, Version

DocFile Viewer utility, CLR Binding Identities

domain-neutral assemblies, Domain-Neutral Assemblies, Domain-Neutral Assemblies, Domain-Neutral Assembly Architecture, Implications of Using Domain-Neutral Code, Implications of Using Domain-Neutral Code, Implications of Using Domain-Neutral Code, Initialization of Types Can Be Slower, Initialization of Types Can Be Slower, Initialization of Types Can Be Slower, Initialization of Types Can Be Slower, Domain-Neutral Code and Assembly Dependencies, Domain-Neutral Code and Assembly Dependencies, Domain-Neutral Code and Assembly Dependencies, Domain-Neutral Code and Assembly Dependencies, CorBindToRuntimeEx, Domain-Neutral Assemblies and the CLR Hosting Interfaces, Domain-Neutral Assemblies and the CLR Hosting Interfaces, Domain-Neutral Assemblies and the CLR Hosting Interfaces

architecture of, Domain-Neutral Assemblies

closure rule, Initialization of Types Can Be Slower

CLR hosting interfaces for, Domain-Neutral Assemblies and the CLR Hosting Interfaces

CorBindToRuntimeEx, Domain-Neutral Code and Assembly Dependencies

dependency issues, Initialization of Types Can Be Slower

determining which assemblies are, Domain-Neutral Assemblies and the CLR Hosting Interfaces

FileLoadExceptions, Initialization of Types Can Be Slower

implications of, overview, Domain-Neutral Assembly Architecture

LoaderOptimization API, CorBindToRuntimeEx

managed v. unmanaged APIs for specifying, Domain-Neutral Assemblies and the CLR Hosting Interfaces

purpose of, Domain-Neutral Assemblies

security policy restrictions, Initialization of Types Can Be Slower

specifying, Domain-Neutral Code and Assembly Dependencies

STARTUP_FLAGS enumeration, Domain-Neutral Code and Assembly Dependencies

static variable access speed, Implications of Using Domain-Neutral Code

type initialization speed, Implications of Using Domain-Neutral Code

unloading prohibited, Implications of Using Domain-Neutral Code

version policy, importance of, Domain-Neutral Code and Assembly Dependencies

domain-neutral code, CLR Initialization and Startup, CLR Initialization and Startup, Loading Code Domain Neutral, Concurrent Garbage Collection, Concurrent Garbage Collection, Concurrent Garbage Collection, Setting the Startup Options Using CorBindToRuntimeEx, Defaults for the CLR Startup Options, Access to Static Data and Members, Application Domain Structure, Domain-Neutral Assemblies, Domain-Neutral Assembly Architecture, Implications of Using Domain-Neutral Code, Implications of Using Domain-Neutral Code, Implications of Using Domain-Neutral Code, Initialization of Types Can Be Slower, Initialization of Types Can Be Slower, Initialization of Types Can Be Slower

application domain static elements, Application Domain Structure

assembly dependencies, Initialization of Types Can Be Slower

closure rule, Initialization of Types Can Be Slower

CorBindToRuntimeEx options, CLR Initialization and Startup, Setting the Startup Options Using CorBindToRuntimeEx

default CLR host default, Defaults for the CLR Startup Options

defined, CLR Initialization and Startup, Concurrent Garbage Collection

implications of, overview, Domain-Neutral Assembly Architecture

loading, Loading Code Domain Neutral

managed host code, Concurrent Garbage Collection

purpose of, Domain-Neutral Assemblies

security policy restrictions, Initialization of Types Can Be Slower

startup settings, Concurrent Garbage Collection

static data with, Access to Static Data and Members

static variable access speed, Implications of Using Domain-Neutral Code

type initialization speed, Implications of Using Domain-Neutral Code

unloading assemblies prohibited, Implications of Using Domain-Neutral Code

DomainUnload events, Step 3: Running Finalizers

downloaded files cache, Shadow Copy Settings, The Shadow Copy Sample

DynamicBase property, Miscellaneous Settings