E

early-bound assemblies, Strong and Weak Assembly Names

EBindPolicyLevels enumeration, The AssemblyBindInfo Structure

environment variables for domain to process associations, Environment Variables

errors., Using Fuslogvw.exe to Understand How Assemblies Are Located (see )

escalation policy, Writing Highly Available Microsoft .NET Framework Applications, Application Domain Isolation and Process Lifetimes, Failure Escalation, Failure Escalation, Failure Escalation, Failure Escalation, Failure Escalation, Failure Escalation, Failure Escalation, Failure Escalation, Critical Finalization, SafeHandles, and Constrained Execution Regions, Critical Finalization, SafeHandles, and Constrained Execution Regions, Critical Finalization, SafeHandles, and Constrained Execution Regions, Critical Finalization, SafeHandles, and Constrained Execution Regions, Specifying Escalation Policy Using the CLR Hosting Interfaces, Specifying Escalation Policy Using the CLR Hosting Interfaces, Setting Policy Using ICLRPolicyManager, Setting Policy Using ICLRPolicyManager, Step 2: Set Actions to Take on Failures, Step 2: Set Actions to Take on Failures, Step 3: Set Timeouts and the Actions to Take for Various Operations, Step 3: Set Timeouts and the Actions to Take for Various Operations, Step 4: Set Any Default Actions, Step 4: Set Any Default Actions, Step 5: Specify Unhandled Exceptions Behavior, Step 5: Specify Unhandled Exceptions Behavior, Step 2: Notify the CLR of Your Implementation Using IHostControl, Use Only the Synchronization Primitives Provided by the .NET Framework, Use Only the Synchronization Primitives Provided by the .NET Framework, Annotate Your Libraries with the HostProtectionAttribute

action options for failures, Failure Escalation

calls to unmanaged code, Use Only the Synchronization Primitives Provided by the .NET Framework

CERs, Critical Finalization, SafeHandles, and Constrained Execution Regions

critical regions of code, Failure Escalation

default action specification, Step 3: Set Timeouts and the Actions to Take for Various Operations

defined, Writing Highly Available Microsoft .NET Framework Applications

disabling the CLR, Failure Escalation

example, Failure Escalation

failure types, Failure Escalation

fast process exits, Step 2: Set Actions to Take on Failures

fatal runtime errors, Failure Escalation

finalizer issues, Critical Finalization, SafeHandles, and Constrained Execution Regions

host protection, Annotate Your Libraries with the HostProtectionAttribute

ICLRPolicyManager for specifying, Specifying Escalation Policy Using the CLR Hosting Interfaces

IHostPolicyManager, Step 5: Specify Unhandled Exceptions Behavior

native handle issues, Critical Finalization, SafeHandles, and Constrained Execution Regions

notifications of actions, Step 5: Specify Unhandled Exceptions Behavior

orphaned locks, Failure Escalation

overview, Application Domain Isolation and Process Lifetimes

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

SetDefaultAction method, Setting Policy Using ICLRPolicyManager, Step 3: Set Timeouts and the Actions to Take for Various Operations

SetUnhandledExceptionPolicy method, Setting Policy Using ICLRPolicyManager, Step 4: Set Any Default Actions

specifying, overview of interfaces for, Specifying Escalation Policy Using the CLR Hosting Interfaces

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

timeouts, Failure Escalation, Step 2: Set Actions to Take on Failures

unhandled exception behavior specification, Step 4: Set Any Default Actions

evidence, Type Visibility, An Overview of Code Access Security, The Core Concepts: Evidence, Permissions, and Policy, Evidence, Evidence, Evidence, Evidence, Runtime Enforcement of Permissions: Permission Demands and the Stack Walk, Step 1: Provide an Initial Implementation of HostSecurityManager, Step 4: Create an Application-Domain-Level Policy Tree, Step 4: Create an Application-Domain-Level Policy Tree, Step 4: Create an Application-Domain-Level Policy Tree, Step 5: Assign Custom Evidence to Assemblies in the Cocoon, Step 5: Assign Custom Evidence to Assemblies in the Cocoon, Step 5: Assign Custom Evidence to Assemblies in the Cocoon, Assigning Evidence Using the Assembly Loading APIs, Assigning Evidence Using the Assembly Loading APIs, Putting It All Together

application domains, associating with, Putting It All Together

assembly-provided, Evidence

assigning to assemblies, Step 4: Create an Application-Domain-Level Policy Tree

CAS, defined, Type Visibility

cocoon sample implementation, Step 1: Provide an Initial Implementation of HostSecurityManager

collection manipulation, Step 4: Create an Application-Domain-Level Policy Tree

defined, An Overview of Code Access Security

determining assembly sources, Step 5: Assign Custom Evidence to Assemblies in the Cocoon

Evidencedisplay.cs sample, Evidence

Evidenceload.cs example, Assigning Evidence Using the Assembly Loading APIs

implementation by objects, Evidence

Load method for assigning, Step 5: Assign Custom Evidence to Assemblies in the Cocoon

ProvideAssemblyEvidence method, Runtime Enforcement of Permissions: Permission Demands and the Stack Walk, Step 4: Create an Application-Domain-Level Policy Tree

relation to permissions and policy, The Core Concepts: Evidence, Permissions, and Policy

serialization of, Assigning Evidence Using the Assembly Loading APIs

sources of, Evidence

zone associations, Step 5: Assign Custom Evidence to Assemblies in the Cocoon

exception handling, Writing Highly Available Microsoft .NET Framework Applications, Application Domain Isolation and Process Lifetimes, Failure Escalation, Failure Escalation, Failure Escalation, Failure Escalation, Failure Escalation, Failure Escalation, Failure Escalation, Failure Escalation, Setting Policy Using ICLRPolicyManager, Step 4: Set Any Default Actions, Use Only the Synchronization Primitives Provided by the .NET Framework

action options for failures, Failure Escalation

add-ins problem, Application Domain Isolation and Process Lifetimes

bubbling up, Failure Escalation

critical regions of code, Failure Escalation

disabling the CLR, Failure Escalation

escalation., Failure Escalation (see )

failure types, Failure Escalation

fatal runtime errors, Failure Escalation

memory requirements problem, Writing Highly Available Microsoft .NET Framework Applications

orphaned locks, Failure Escalation

SetUnhandledExceptionPolicy method, Setting Policy Using ICLRPolicyManager

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

unhandled exception behavior specification, Step 4: Set Any Default Actions

exceptions, Using Fuslogvw.exe to Understand How Assemblies Are Located, Failure Escalation, Step 2: Specifying Which Host Protection Categories to Block

assembly loading, Using Fuslogvw.exe to Understand How Assemblies Are Located

handling., Failure Escalation (see )

host protection, Step 2: Specifying Which Host Protection Categories to Block

ExecApp.cpp example, Loading Assemblies Using ICLRRuntimeHost

ExecuteApplication, CorBindToRuntimeEx and ICLRRuntimeHost

ExecuteAssemblyByName method of AppDomain, Using Assembly.Load and Related Methods

ExecuteInDefaultAppDomain method, CorBindToRuntimeEx and ICLRRuntimeHost, The Loadfrom Context and Dependencies

ExecuteInDomain, CorBindToRuntimeEx and ICLRRuntimeHost

exiting processes, Failure Escalation

extensibility, CLR Hosts and Other Extensible Applications, The <requiredRuntime> Element and .NET Framework 1.0, Loading Assemblies in Extensible Applications, Loading Assemblies by Assembly Identity, Loading Assemblies by Assembly Identity, Loading Assemblies by Assembly Identity, Loading Assemblies by Assembly Identity, System.Reflection.Assembly and CLR Remote Calls, Recommendations for Loading Assemblies in Extensible Applications, Capturing Assembly Load Events, Determining Which Version of the CLR Was Used to Build an Assembly, Determining Which Version of the CLR Was Used to Build an Assembly

.NET Framework unification, Determining Which Version of the CLR Was Used to Build an Assembly

add-in issues., Recommendations for Loading Assemblies in Extensible Applications (see )

application domain manager role, Loading Assemblies by Assembly Identity

application domain role, Loading Assemblies by Assembly Identity

applications of, CLR Hosts and Other Extensible Applications

architecture for, design points, Loading Assemblies by Assembly Identity

assembly loading issues, Loading Assemblies in Extensible Applications

assembly loading recommendations, System.Reflection.Assembly and CLR Remote Calls

choice of CLR version, Determining Which Version of the CLR Was Used to Build an Assembly

locations for add-in assemblies, Loading Assemblies by Assembly Identity

overview of, The <requiredRuntime> Element and .NET Framework 1.0

versions of CLR, effects of, Capturing Assembly Load Events