Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/core/dependency-loading/loading-managed.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,8 +49,8 @@ The following algorithm describes how the runtime loads a managed assembly.
- Check its `cache-by-name`.
- Call the <xref:System.Runtime.Loader.AssemblyLoadContext.Load*?displayProperty=nameWithType> function.
- Check the <xref:System.Runtime.Loader.AssemblyLoadContext.Default?displayProperty=nameWithType> instance's cache and run [managed assembly default probing](default-probing.md#managed-assembly-default-probing) logic. If an assembly is newly loaded, a reference is added to the <xref:System.Runtime.Loader.AssemblyLoadContext.Default?displayProperty=nameWithType> instance's `cache-by-name`.
- Raise the <xref:System.Runtime.Loader.AssemblyLoadContext.Resolving?displayProperty=nameWithType> event for the active AssemblyLoadContext.
- Raise the <xref:System.AppDomain.AssemblyResolve?displayProperty=nameWithType> event.
- Raise the <xref:System.Runtime.Loader.AssemblyLoadContext.Resolving?displayProperty=nameWithType> event for the active AssemblyLoadContext. Handlers are invoked in registration order. The first handler that returns a non-null assembly ends the resolution.
- Raise the <xref:System.AppDomain.AssemblyResolve?displayProperty=nameWithType> event. Handlers are invoked in registration order. The first handler that returns a non-null assembly ends the resolution.

3. For the other types of loads, the `active` <xref:System.Runtime.Loader.AssemblyLoadContext> loads the assembly in the following priority order:

Expand Down
Loading