book

Customizing the Microsoft® .NET Framework Common Language Runtime

Name: Customizing the Microsoft® .NET Framework Common Language Runtime
Author: Steven Pratschner
ISBN: 9780735619883

by Steven Pratschner

February 2005

Intermediate to advanced

400 pages

14h

English

Microsoft Press

Read now

Unlock full access

Customizing the Microsoft® .NET Framework Common Language Runtime
Foreword
Acknowledgments
Introduction
What Makes This .NET Framework Book Unique?The .NET Framework 2.0 PrereleasesSample Code and System RequirementsComments, Corrections, and Support
1. CLR Hosts and Other Extensible Applications
Summary
2. A Tour of the CLR Hosting API
CorBindToRuntimeEx and ICLRRuntimeHostCLR Hosting ManagersCLR Initialization and StartupOther Unmanaged Functions on mscoree.dllHosting Manager DiscoveryDiscovering Host-Implemented ManagersStep 1: The Host Supplies a Host Control ClassStep 2: The CLR Queries the Host Control ClassObtaining CLR-Implemented ManagersOverview of the Hosting ManagersAssembly LoadingCustomizing Failure BehaviorProgramming Model EnforcementMemory and Garbage CollectionThreading and SynchronizationOther Hosting API FeaturesLoading Code Domain NeutralThread Pool ManagementI/O Completion ManagementDebugging Services ManagementApplication Domain ManagementCLR Event HandlingSummary
3. Controlling CLR Startup and Shutdown
The CLR Startup Configuration SettingsVersionSide by Side: A Technique to Avoid DLL HellThe Side-by-Side Architecture of the .NET Framework.NET Framework Registry KeysThe Versioned Installation DirectoryThe Global Assembly CacheThe CLR Startup Shim.NET Framework UpdatesChoosing Your Strategy: Fix or FloatThe Server and Workstation BuildsConcurrent Garbage CollectionDomain-Neutral CodeSetting the Startup Options Using CorBindToRuntimeExStarting the CLRHandling Failures from CorBindToRuntimeExDeferring CLR Initialization and StartupThe CLR and Process LifetimeSummary
4. Using the Default CLR Host
Invoking the Default Host: Running Managed ExecutablesInvoking the Default Host: Activating Managed Types Through COM InteropDefaults for the CLR Startup OptionsSelecting a CLR VersionRunning Managed ExecutablesUpgradesActivating Managed Types Through COM InteropCustomizing the Default Host Using Configuration FilesConcurrent Garbage CollectionBuild TypeChanging the Build Type on Older Versions of the CLRVersionThe <supportedRuntime> ElementThe <requiredRuntime> Element and .NET Framework 1.0Summary
5. Using Application Domains Effectively
The Role of Application DomainsType Safety and VerificationApplication IsolationType VisibilityConfiguration DataSecurity SettingsAccess to Static Data and MembersRuntime Concepts Not Isolated by Application DomainsApplication Domain StructureAssembly ListSecurity PolicyApplication Domain PropertiesStatics for Domain-Neutral AssembliesProxies for Remote CallsThe Default Application DomainThe AppDomainViewer ToolGuidelines for Partitioning a Process into Multiple Application DomainsCode UnloadingCross-Domain CommunicationSample Application Domain BoundariesASP.NETSQL ServerInternet ExplorerApplication Domain ManagersCreating an Application Domain ManagerAssociating an Application Domain Manager with a ProcessThe CLR Hosting APIsCalling an Application Domain Manager from Unmanaged CodeStep 1: Setting Initialization Flags to Register With HostStep 2: Implement IHostControl::SetAppDomainManagerEnvironment VariablesCreating Application DomainsApplication Domains and ThreadsThe CLR Thread PoolUnloading Application DomainsStep 1: Aborting the Threads Running in the DomainStep 2: Raising an Unload EventStep 3: Running FinalizersStep 4: Freeing the Internal CLR Data StructuresExceptions Related to Unloading Application DomainsReceiving Application Domain Unload EventsReceiving Domain Unload Events Using the IActionOnCLREvent InterfaceSummary
6. Configuring Application Domains
Application Domain Configuration SettingsPrivate Assembly Directory SettingsCustomizing the ApplicationBase Directory StructureTurning Off ApplicationBase SearchingConfiguration File SettingsShadow Copy SettingsTurning on Shadow CopySpecifying the Location for the Copied FilesSpecifying Which Files Are CopiedThe Shadow Copy SampleAssembly Binding SettingsMiscellaneous SettingsLicenseFileLoaderOptimizationDynamicBaseDisallowCodeDownloadActivationArgumentsAppDomainInitializer and AppDomainInitializerArgumentsCustomizing Application Domain Creation Using System.AppDomainManagerStep 1: Call AppDomainManager.CreateDomainStep 2: Create a New Instance of the Application Domain ManagerStep 3: Call AppDomainManager.InitializeNewDomainStep 4: Get the ApplicationActivatorStep 5: Get the HostExecutionContextManagerStep 6: Get the HostSecurityManagerSummary

7. Loading Assemblies in Extensible Applications
Concepts and TerminologyStrong and Weak Assembly NamesEarly-Bound and Late-Bound ReferencesFully Specified and Partially Specified ReferencesVersion PolicyLoading Assemblies by Assembly IdentityArchitecture of an Extensible Application RevisitedSystem.Reflection.Assembly and CLR Remote CallsRecommendations for Loading Assemblies in Extensible ApplicationsStep 1: The Extensible Application Is Made Aware of the New Add-InStep 2: An Application Domain Is Chosen in Which to Load the New Add-InStep 3: The Application Domain Manager in the Target Domain Is Called to Load the Add-InStep 4: The Application Domain Manager in the Target Domain Loads the Add-InUsing Assembly.Load and Related MethodsSpecifying Assembly Identities as StringsSpecifying Assembly Identities Using System.Reflection.AssemblyNameHow the CLR Locates AssembliesHow the CLR Locates Assemblies with Weak NamesHow the CLR Locates Assemblies with Strong NamesUsing System.Reflection.Assembly to Determine an Assembly’s Location on DiskUsing Fuslogvw.exe to Understand How Assemblies Are LocatedCommon Assembly Loading ExceptionsPartially Specified Assembly ReferencesLoading Assemblies by FilenameSubtleties of Assembly.LoadFromLoadFrom’s Second BindBinding Contexts and Type IdentityLoading Multiple Files with the Same NameThe Loadfrom Context and DependenciesThe ReflectionOnly APIsLoading Assemblies Using ICLRRuntimeHostCapturing Assembly Load EventsVersioning Considerations for Extensible ApplicationsDetermining Which Version of the CLR Was Used to Build an AssemblyThe Extensible Application Chooses the VersionMicrosoft .NET Framework UnificationOverriding UnificationSummary
8. Customizing How Assemblies Are Loaded
The Cocoon Deployment ModelCLR Binding IdentitiesObtaining Binding IdentitiesStep 1: Obtaining a Pointer to ICLRAssemblyIdentityManagerStep 2: Calling GetBindingIdentityFromFile (or Stream)The Makecocoon.exe ProgramImplementing an Assembly Loading ManagerImplementing the IHostAssemblyManager InterfaceSpecifying Non-Host-Loaded AssembliesReturning an Assembly StoreImplementing the IHostAssemblyStore InterfaceResolving Assembly ReferencesThe AssemblyBindInfo StructureThe EBindPolicyLevels EnumerationAssociating Host-Specific Data with an AssemblyAssigning Assembly IdentityLoading Assemblies from a CocoonResolving Module ReferencesBringing It All TogetherOpening the Cocoon FileInitializing the CLRCreating the Assembly Loading Manager and Host Control ObjectInvoking the Hosted ApplicationCustomizing How Assemblies Are Loaded Using Only Managed CodeThe Load(byte[]...) MethodsThe AssemblyResolve EventThe Runcocoonm SampleSupporting Multifile AssembliesSummary
9. Domain-Neutral Assemblies
Domain-Neutral Assembly ArchitectureImplications of Using Domain-Neutral CodeDomain-Neutral Code Cannot Be UnloadedAccess to Static Member Variables Is SlowerInitialization of Types Can Be SlowerSecurity Policy Must Be Consistent Across All Application DomainsThe Set of Domain-Neutral Assemblies Must Form a ClosureDomain-Neutral Code and Assembly DependenciesSpecifying Which Assemblies Are Loaded Domain NeutralCorBindToRuntimeExThe Loader Optimization APIDomain-Neutral Assemblies and the CLR Hosting InterfacesDetermining Whether an Assembly Has Been Loaded Domain NeutralSummary
10. Extending the CLR Security System to Protect Your Extensible Application
An Overview of Code Access SecurityThe Core Concepts: Evidence, Permissions, and PolicyEvidencePolicyPolicy LevelsDefault CAS PolicyPermissionsRuntime Enforcement of Permissions: Permission Demands and the Stack WalkCustomizing the Code Access Security System Using a HostSecurityManagerCode Access Security in the Cocoon HostStep 1: Provide an Initial Implementation of HostSecurityManagerStep 2: Create Custom EvidenceStep 3: Create a Custom Membership ConditionStep 4: Create an Application-Domain-Level Policy TreeStep 5: Assign Custom Evidence to Assemblies in the CocoonAssigning Evidence Using the Assembly Loading APIsPutting It All TogetherAssociating Evidence with an Application DomainThe AllowPartiallyTrustedCallers AttributeSummary
11. Writing Highly Available Microsoft .NET Framework Applications
Application Domain Isolation and Process LifetimesFailure EscalationCritical Finalization, SafeHandles, and Constrained Execution RegionsSpecifying Escalation Policy Using the CLR Hosting InterfacesSetting Policy Using ICLRPolicyManagerStep 1: Obtain a ICLRPolicyManager Interface PointerStep 2: Set Actions to Take on FailuresStep 3: Set Timeouts and the Actions to Take for Various OperationsStep 4: Set Any Default ActionsStep 5: Specify Unhandled Exceptions BehaviorReceiving Notifications Through IHostPolicyManagerStep 1: Provide an Implementation of IHostPolicyManagerStep 2: Notify the CLR of Your Implementation Using IHostControlGuidelines for Writing Highly Available Managed CodeUse SafeHandles to Encapsulate All Native HandlesUse Only the Synchronization Primitives Provided by the .NET FrameworkEnsure That Calls to Unmanaged Code Return to the CLRAnnotate Your Libraries with the HostProtectionAttributeSummary
12. Enforcing Application-Specific Programming Model Constraints
The Host Protection CategoriesSynchronizationShared StateExternal Process ManagementSelf-Affecting Process ManagementSelf-Affecting ThreadingExternal ThreadingSecurity InfrastructureUser Interface"May Leak on Abort"Using the Host Protection ManagerHost Protection in the Cocoon Deployment ModelStep 1: Obtaining the ICLRHostProtectionManager Interface PointerStep 2: Specifying Which Host Protection Categories to BlockSummary
13. Managing How the CLR Uses Memory
Integrating the CLR with Custom Memory ManagersVirtual Memory ManagementHeap ManagementFile MappingReporting Memory Status to the CLRThe GetMemoryLoad MethodThe ICLRMemoryNotificationCallback InterfaceConfiguring the CLR Garbage CollectorPartitioning the Garbage Collector’s HeapGathering Garbage Collection StatisticsInitiating Garbage CollectionsReceiving Notifications Through the IHostGCManager InterfaceSummary
14. Integrating the CLR with Custom Schedulers and Thread Pools
The Task AbstractionControlling the Execution of TasksThe Life Cycle of a TaskHooking Calls That Enter and Leave the CLRThe Synchronization ManagerReplacing the CLR’s Thread PoolSummary
About the Author
Index
About the Author
Copyright

Overview

Get advanced programming techniques and guidelines to exploit the flexibility and customizability of the common language runtime for a variety of applications, from databases to cell phones.

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 0735619883Errata

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills