S

SafeHandles, Critical Finalization, SafeHandles, and Constrained Execution Regions, Step 2: Notify the CLR of Your Implementation Using IHostControl

security, Application Domain Structure, Cross-Domain Communication, Creating Application Domains, Step 4: Get the ApplicationActivator, Initialization of Types Can Be Slower, Extending the CLR Security System to Protect Your Extensible Application, An Overview of Code Access Security, Policy, Runtime Enforcement of Permissions: Permission Demands and the Stack Walk, Customizing the Code Access Security System Using a HostSecurityManager, Putting It All Together, Putting It All Together, Associating Evidence with an Application Domain, Enforcing Application-Specific Programming Model Constraints, External Threading

application domain data elements for, Application Domain Structure

blocking functionality., Enforcing Application-Specific Programming Model Constraints (see )

code access., Associating Evidence with an Application Domain (see )

CreateDomain method parameter for, Creating Application Domains

domain-neutral code requirements for, Initialization of Types Can Be Slower

evidence, CAS., Putting It All Together (see )

HostSecurityManager class, Step 4: Get the ApplicationActivator, Runtime Enforcement of Permissions: Permission Demands and the Stack Walk

impersonation, External Threading

manifests, Customizing the Code Access Security System Using a HostSecurityManager

overview of, Extending the CLR Security System to Protect Your Extensible Application

partially trusted code, An Overview of Code Access Security

permissions., Putting It All Together (see )

policy., Policy (see )

shared assembly issues, Cross-Domain Communication

semaphores, The Synchronization Manager

server build type, .NET Framework Updates, The Server and Workstation Builds, Concurrent Garbage Collection

concurrent garbage collection, The Server and Workstation Builds

default CLR host options, Concurrent Garbage Collection

defined, .NET Framework Updates

service pack version control issues, .NET Framework Updates

SetAppDomainManager method, Step 1: Setting Initialization Flags to Register With Host

SetAppDomainManagerType method, Associating an Application Domain Manager with a Process

SetHostControl method, Discovering Host-Implemented Managers

shadow copies, Application Domain Configuration Settings, Configuration File Settings, Configuration File Settings, Configuration File Settings, Configuration File Settings, Shadow Copy Settings, Shadow Copy Settings, Shadow Copy Settings, Shadow Copy Settings, Specifying the Location for the Copied Files, Specifying the Location for the Copied Files, Specifying the Location for the Copied Files, Specifying Which Files Are Copied, The Shadow Copy Sample, The Shadow Copy Sample, The Shadow Copy Sample, DynamicBase

advantages of, Configuration File Settings

AppDomainSetup properties for, Configuration File Settings

custom locations for, setting, Specifying the Location for the Copied Files, The Shadow Copy Sample

defined, Application Domain Configuration Settings

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

dynamic assemblies with, DynamicBase

enabling, steps for, Shadow Copy Settings

overview of, Configuration File Settings

sample application, Specifying Which Files Are Copied

ShadowCopiesDirectory property, Specifying the Location for the Copied Files

ShadowCopyFiles property, Configuration File Settings

specifying file locations, Shadow Copy Settings, The Shadow Copy Sample

specifying files to be copied, Specifying the Location for the Copied Files

turning on, Shadow Copy Settings

shared assemblies, Cross-Domain Communication

shared state, Programming Model Enforcement, Failure Escalation, Use Only the Synchronization Primitives Provided by the .NET Framework, Synchronization

blocking with host protection manager, Programming Model Enforcement

escalation policy, Failure Escalation, Use Only the Synchronization Primitives Provided by the .NET Framework

host protection of, Synchronization

side by side architecture, CLR Initialization and Startup, Version, Version, Side by Side: A Technique to Avoid DLL Hell, Side by Side: A Technique to Avoid DLL Hell, The Side-by-Side Architecture of the .NET Framework, The Side-by-Side Architecture of the .NET Framework, .NET Framework Registry Keys, The Versioned Installation Directory, The Global Assembly Cache

.NET Framework approach to, Side by Side: A Technique to Avoid DLL Hell

advantages of, Version

applications with, Version

defined, CLR Initialization and Startup

directories for versions, .NET Framework Registry Keys

GAC issues, The Versioned Installation Directory

installation of .NET Framework, The Side-by-Side Architecture of the .NET Framework

platform level, Side by Side: A Technique to Avoid DLL Hell

registry keys, .NET, The Side-by-Side Architecture of the .NET Framework

startup shims, The Global Assembly Cache

single bug fix releases, The CLR Startup Shim

Skip Verification permission, Type Safety and Verification

SQL Server 2005, Assembly Loading, Sample Application Domain Boundaries, Customizing How Assemblies Are Loaded, Enforcing Application-Specific Programming Model Constraints, Managing How the CLR Uses Memory, Virtual Memory Management, Integrating the CLR with Custom Schedulers and Thread Pools, The Synchronization Manager, The Synchronization Manager, Replacing the CLR’s Thread Pool

application domains with, Sample Application Domain Boundaries

assembly loading issues, Assembly Loading, Customizing How Assemblies Are Loaded

fiber mode, Integrating the CLR with Custom Schedulers and Thread Pools

host protection model, Enforcing Application-Specific Programming Model Constraints

memory manager for, Managing How the CLR Uses Memory, Virtual Memory Management

scalability and CLR overview, Replacing the CLR’s Thread Pool

synchronization manager, need for, The Synchronization Manager

thread pool manager for, The Synchronization Manager

stability, failure policy manager for, Customizing Failure Behavior

stack walks, Permissions, Runtime Enforcement of Permissions: Permission Demands and the Stack Walk, Putting It All Together

Start method, CorBindToRuntimeEx and ICLRRuntimeHost, CLR Initialization and Startup

calling of during initialization, CLR Initialization and Startup

defined, CorBindToRuntimeEx and ICLRRuntimeHost

startup, CLR Hosting Managers, Controlling CLR Startup and Shutdown, Controlling CLR Startup and Shutdown, Version, Version, Version, The Side-by-Side Architecture of the .NET Framework, .NET Framework Registry Keys, The Versioned Installation Directory, The CLR Startup Shim, .NET Framework Updates, The Server and Workstation Builds, Concurrent Garbage Collection, Domain-Neutral Code, Domain-Neutral Code, Domain-Neutral Code, Domain-Neutral Code, Setting the Startup Options Using CorBindToRuntimeEx, Setting the Startup Options Using CorBindToRuntimeEx, Setting the Startup Options Using CorBindToRuntimeEx, Handling Failures from CorBindToRuntimeEx, Handling Failures from CorBindToRuntimeEx, Handling Failures from CorBindToRuntimeEx, Handling Failures from CorBindToRuntimeEx, Deferring CLR Initialization and Startup, Deferring CLR Initialization and Startup, Using the Default CLR Host, Initializing the CLR, Initializing the CLR

advantages of writing hosts for, Controlling CLR Startup and Shutdown

build type options, .NET Framework Updates, Domain-Neutral Code

cocoon example, Initializing the CLR

COM interoperability issues, Handling Failures from CorBindToRuntimeEx

concurrent garbage collection, The Server and Workstation Builds, Domain-Neutral Code

CorBindToRuntimeEx for setting options, Domain-Neutral Code

default CLR host for., Using the Default CLR Host (see )

deferring initialization, Handling Failures from CorBindToRuntimeEx

domain-neutral code settings, Concurrent Garbage Collection, Setting the Startup Options Using CorBindToRuntimeEx

failures, handling, Handling Failures from CorBindToRuntimeEx

GAC issues, The Versioned Installation Directory

ICLRRuntimeHost for starting CLR, Setting the Startup Options Using CorBindToRuntimeEx

initialization, CLR Hosting Managers, Initializing the CLR

installation directories, .NET Framework Registry Keys

lazy loading of CLR, Handling Failures from CorBindToRuntimeEx

LockClrVersion function, Deferring CLR Initialization and Startup

multiple CLR versions problem, Version

preventing CLR loading, Deferring CLR Initialization and Startup

registry keys, The Side-by-Side Architecture of the .NET Framework

settings, overview of, Controlling CLR Startup and Shutdown

shims., The CLR Startup Shim (see )

side by side model, Version

starting CLR, Setting the Startup Options Using CorBindToRuntimeEx

version settings, Version, Domain-Neutral Code

startup shims, CLR Initialization and Startup, The Global Assembly Cache, The Global Assembly Cache, The Global Assembly Cache, The CLR Startup Shim, The CLR Startup Shim, The CLR Startup Shim, The CLR Startup Shim, The CLR Startup Shim, The CLR Startup Shim, The CLR Startup Shim, The CLR Startup Shim, The CLR Startup Shim, The CLR Startup Shim, The CLR Startup Shim, The CLR Startup Shim, The CLR Startup Shim, .NET Framework Updates, .NET Framework Updates, .NET Framework Updates, Deferring CLR Initialization and Startup, Using the Default CLR Host, Invoking the Default Host: Activating Managed Types Through COM Interop, Invoking the Default Host: Activating Managed Types Through COM Interop, Upgrades

automatic version matching, The CLR Startup Shim

backward compatibility, The Global Assembly Cache, The CLR Startup Shim

class libraries, loading, The CLR Startup Shim

COM interoperability, version selection of CLR, Upgrades

CorBindToRuntimeEx with, The CLR Startup Shim

default CLR host, The CLR Startup Shim, The CLR Startup Shim, Invoking the Default Host: Activating Managed Types Through COM Interop

default host for managed executables, Using the Default CLR Host, Invoking the Default Host: Activating Managed Types Through COM Interop

defined, CLR Initialization and Startup

feature releases, .NET Framework Updates

file containing, The Global Assembly Cache

InstallRoot value, The CLR Startup Shim

loading of DLLs, The CLR Startup Shim

LockClrVersion function, Deferring CLR Initialization and Startup

mscorlib.dll, loading, The CLR Startup Shim

path construction, The CLR Startup Shim

server build restrictions, .NET Framework Updates

service packs, .NET Framework Updates

single bug fix releases, The CLR Startup Shim

updates to framework, The CLR Startup Shim

version behavior differences, The CLR Startup Shim

versioning issues, The Global Assembly Cache

STARTUP_FLAGS enumeration, Domain-Neutral Code and Assembly Dependencies

static data, Access to Static Data and Members

static variables, Implications of Using Domain-Neutral Code

Stop method of ICLRRuntimeHost, CorBindToRuntimeEx and ICLRRuntimeHost, The CLR and Process Lifetime

stopping CLR, CorBindToRuntimeEx and ICLRRuntimeHost, The CLR and Process Lifetime

string-based assembly identities, The Cocoon Deployment Model

(see also )

strong names, Concepts and Terminology, How the CLR Locates Assemblies with Weak Names

defined, Concepts and Terminology

locating assemblies with, How the CLR Locates Assemblies with Weak Names

structured storage files, The Cocoon Deployment Model, CLR Binding Identities

defined, The Cocoon Deployment Model

viewing, utility for, CLR Binding Identities

subprocesses., DisallowCodeDownload (see )

supportedRuntime element, Version

svrhost.cpp, Build Type

synchronization, Programming Model Enforcement, Synchronization, The Synchronization Manager, The Synchronization Manager

blocking with host protection manager, Programming Model Enforcement

host protection of, Synchronization

managers., The Synchronization Manager (see )

primitives., The Synchronization Manager (see )

synchronization managers, CLR Hosting Managers, Memory and Garbage Collection, Integrating the CLR with Custom Schedulers and Thread Pools, Hooking Calls That Enter and Leave the CLR, The Synchronization Manager, The Synchronization Manager, The Synchronization Manager, The Synchronization Manager, The Synchronization Manager, The Synchronization Manager, The Synchronization Manager, The Synchronization Manager, The Synchronization Manager, The Synchronization Manager, The Synchronization Manager

auto reset events, The Synchronization Manager

critical sections, The Synchronization Manager

defined, CLR Hosting Managers

ICLRSyncManager, The Synchronization Manager

IHostAutoEvent, The Synchronization Manager

IHostCrst, The Synchronization Manager

IHostManualEvent, The Synchronization Manager

IHostSemaphore, The Synchronization Manager

IHostSyncManager, The Synchronization Manager

manual events, The Synchronization Manager

overview of, Memory and Garbage Collection

primitive types created by, The Synchronization Manager

purpose of, Integrating the CLR with Custom Schedulers and Thread Pools, Hooking Calls That Enter and Leave the CLR

semaphores, The Synchronization Manager

synchronization primitives, Failure Escalation, Failure Escalation, Use Only the Synchronization Primitives Provided by the .NET Framework, The Synchronization Manager, The Synchronization Manager, The Synchronization Manager, The Synchronization Manager, The Synchronization Manager

auto reset events, The Synchronization Manager

critical sections, The Synchronization Manager

detecting, Failure Escalation

guidelines for, Use Only the Synchronization Primitives Provided by the .NET Framework

manual events, The Synchronization Manager

orphaned locks, Failure Escalation

semaphores, The Synchronization Manager

supplying to CLR., The Synchronization Manager (see )

System.Reflection.Assembly, How the CLR Locates Assemblies with Strong Names