Skip to content

Document default probing behavior in AssemblyLoadContext for LoadFromPath/LoadFromStream #51185

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adegeo merged 5 commits into from
Jan 16, 2026
Merged

Document default probing behavior in AssemblyLoadContext for LoadFromPath/LoadFromStream #51185

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
b25b1a4
Initial plan
Copilot Jan 15, 2026
6dc97a7
Update loading-managed.md to clarify default probing behavior for non…
Copilot Jan 15, 2026
c8ee833
Update docs/core/dependency-loading/loading-managed.md
elinor-fung Jan 15, 2026
019631d
Update default-probing.md to clarify precedence of TPA and APP_PATHS
Copilot Jan 15, 2026
8a6e9ff
Update docs/core/dependency-loading/loading-managed.md
elinor-fung Jan 15, 2026
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
2 changes: 2 additions & 0 deletions docs/core/dependency-loading/default-probing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,8 @@ When probing to locate a managed assembly, the <xref:System.Runtime.Loader.Assem
- Files matching the <xref:System.Reflection.AssemblyName.Name?displayProperty=nameWithType> in `TRUSTED_PLATFORM_ASSEMBLIES` (after removing file extensions).
- Assembly files in `APP_PATHS` with common file extensions.

When loading in the default <xref:System.Runtime.Loader.AssemblyLoadContext>, assemblies found in `TRUSTED_PLATFORM_ASSEMBLIES` or `APP_PATHS` take precedence over a specified path or raw assembly object. For example, if you call <xref:System.Runtime.Loader.AssemblyLoadContext.LoadFromStream%2A?displayProperty=nameWithType> or <xref:System.Runtime.Loader.AssemblyLoadContext.LoadFromAssemblyPath%2A?displayProperty=nameWithType> on the default <xref:System.Runtime.Loader.AssemblyLoadContext> and an assembly with a matching name exists in `TRUSTED_PLATFORM_ASSEMBLIES` or `APP_PATHS`, the runtime loads the assembly from those locations instead of from the specified stream or path.

## Satellite (resource) assembly probing

To find a satellite assembly for a specific culture, construct a set of file paths.
Expand Down
1 change: 1 addition & 0 deletions docs/core/dependency-loading/loading-managed.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,7 @@ The following algorithm describes how the runtime loads a managed assembly.
3. For the other types of loads, the `active` <xref:System.Runtime.Loader.AssemblyLoadContext> loads the assembly in the following priority order:

- Check its `cache-by-name`.
- If the `active` <xref:System.Runtime.Loader.AssemblyLoadContext> is <xref:System.Runtime.Loader.AssemblyLoadContext.Default%2A?displayProperty=nameWithType>, run the [default probing logic for managed assemblies](default-probing.md#managed-assembly-default-probing).
- Load from the specified path or raw assembly object. If an assembly is newly loaded, a reference is added to the `active` <xref:System.Runtime.Loader.AssemblyLoadContext> instance's `cache-by-name`.

4. In either case, if an assembly is newly loaded, then the <xref:System.AppDomain.AssemblyLoad?displayProperty=nameWithType> event is raised.