Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://learn.microsoft.com/en-us/dotnet/core/dependency-loading/loading-managed below:

Managed assembly loading algorithm - .NET Core - .NET

Managed assemblies are located and loaded with an algorithm that has various stages.

All managed assemblies except satellite assemblies and WinRT assemblies use the same algorithm.

The most common mechanism to trigger a managed assembly load is a static assembly reference. These references are inserted by the compiler whenever code uses a type defined in another assembly. These assemblies are loaded (load-by-name) as needed by the runtime. The exact timing of when the static assembly references are loaded is unspecified. It can vary between runtime versions and is influenced by optimizations like inlining.

The direct use of the following APIs will also trigger loads:

The following algorithm describes how the runtime loads a managed assembly.

1. Determine the active AssemblyLoadContext.

   • For a static assembly reference, the active AssemblyLoadContext is the instance that loaded the referring assembly.
   • Preferred APIs make the active AssemblyLoadContext explicit.
   • Other APIs infer the active AssemblyLoadContext. For these APIs, the AssemblyLoadContext.CurrentContextualReflectionContext property is used. If its value is null, then the inferred AssemblyLoadContext instance is used.
   • See the table in the When are managed assemblies loaded? section.

2. For the Load-by-name methods, the active AssemblyLoadContext loads the assembly in the following priority order:

   • Check its cache-by-name.
   • Call the AssemblyLoadContext.Load function.
   • Check the AssemblyLoadContext.Default instance's cache and run managed assembly default probing logic. If an assembly is newly loaded, a reference is added to the AssemblyLoadContext.Default instance's cache-by-name.
   • Raise the AssemblyLoadContext.Resolving event for the active AssemblyLoadContext.
   • Raise the AppDomain.AssemblyResolve event.

3. For the other types of loads, the active AssemblyLoadContext loads the assembly in the following priority order:

   • Check its cache-by-name.
   • Load from the specified path or raw assembly object. If an assembly is newly loaded, a reference is added to the active AssemblyLoadContext instance's cache-by-name.

4. In either case, if an assembly is newly loaded, then the AppDomain.AssemblyLoad event is raised.

Collaborate with us on GitHub

Was this page helpful?

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4