- Customizing the Microsoft® .NET Framework Common Language Runtime
- Foreword
- Acknowledgments
- Introduction
- 1. CLR Hosts and Other Extensible Applications
- 2. A Tour of the CLR Hosting API
- CorBindToRuntimeEx and ICLRRuntimeHost
- CLR Hosting Managers
- CLR Initialization and Startup
- Other Unmanaged Functions on mscoree.dll
- Hosting Manager Discovery
- Overview of the Hosting Managers
- Summary
- 3. Controlling CLR Startup and Shutdown
- The CLR Startup Configuration Settings
- Setting the Startup Options Using CorBindToRuntimeEx
- Starting the CLR
- Handling Failures from CorBindToRuntimeEx
- Deferring CLR Initialization and Startup
- The CLR and Process Lifetime
- Summary
- 4. Using the Default CLR Host
- 5. Using Application Domains Effectively
- The Role of Application Domains
- Application Domain Structure
- Guidelines for Partitioning a Process into Multiple Application Domains
- Application Domain Managers
- Application Domains and Threads
- Unloading Application Domains
- Summary
- 6. Configuring Application Domains
- 7. Loading Assemblies in Extensible Applications
- Concepts and Terminology
- Loading Assemblies by Assembly Identity
- Architecture of an Extensible Application Revisited
- System.Reflection.Assembly and CLR Remote Calls
- Recommendations for Loading Assemblies in Extensible Applications
- Step 1: The Extensible Application Is Made Aware of the New Add-In
- Step 2: An Application Domain Is Chosen in Which to Load the New Add-In
- Step 3: The Application Domain Manager in the Target Domain Is Called to Load the Add-In
- Step 4: The Application Domain Manager in the Target Domain Loads the Add-In
- Using Assembly.Load and Related Methods
- How the CLR Locates Assemblies
- Using Fuslogvw.exe to Understand How Assemblies Are Located
- Common Assembly Loading Exceptions
- Partially Specified Assembly References
- Architecture of an Extensible Application Revisited
- Loading Assemblies by Filename
- Loading Assemblies Using ICLRRuntimeHost
- Capturing Assembly Load Events
- Versioning Considerations for Extensible Applications
- Summary
- 8. Customizing How Assemblies Are Loaded
- 9. Domain-Neutral Assemblies
- 10. Extending the CLR Security System to Protect Your Extensible Application
- An Overview of Code Access Security
- Customizing the Code Access Security System Using a HostSecurityManager
- Code Access Security in the Cocoon Host
- Associating Evidence with an Application Domain
- The AllowPartiallyTrustedCallers Attribute
- Summary
- 11. Writing Highly Available Microsoft .NET Framework Applications
- 12. Enforcing Application-Specific Programming Model Constraints
- 13. Managing How the CLR Uses Memory
- 14. Integrating the CLR with Custom Schedulers and Thread Pools
- About the Author
- Index
- About the Author
- Copyright
N
- naming assemblies., Concepts and Terminology, Concepts and Terminology, Version Policy, Using Assembly.Load and Related Methods, Specifying Assembly Identities as Strings, How the CLR Locates Assemblies, How the CLR Locates Assemblies with Weak Names, Partially Specified Assembly References, Partially Specified Assembly References, Associating Host-Specific Data with an Assembly
- (see also )
- AssemblyName class, Version Policy, Specifying Assembly Identities as Strings
- partially specifying references, Partially Specified Assembly References
- specification as strings, Using Assembly.Load and Related Methods
- strong names, Concepts and Terminology, How the CLR Locates Assemblies with Weak Names
- weak names, Concepts and Terminology, How the CLR Locates Assemblies, Partially Specified Assembly References
- naming types, Concepts and Terminology
- native handles, Critical Finalization, SafeHandles, and Constrained Execution Regions, Step 2: Notify the CLR of Your Implementation Using IHostControl
- nonconcurrent garbage collection, The Server and Workstation Builds, Domain-Neutral Code
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.