From b25b1a43890dd27dc3b41cd736f0408083e826cf Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 15 Jan 2026 19:20:58 +0000 Subject: [PATCH 1/5] Initial plan From 6dc97a7930bd16390e493de24bf2dfa03c8a46e9 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 15 Jan 2026 19:24:39 +0000 Subject: [PATCH 2/5] Update loading-managed.md to clarify default probing behavior for non-name loads Co-authored-by: elinor-fung <47805090+elinor-fung@users.noreply.github.com> --- docs/core/dependency-loading/loading-managed.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/core/dependency-loading/loading-managed.md b/docs/core/dependency-loading/loading-managed.md index 2d083a2f07ac4..fa07035942131 100644 --- a/docs/core/dependency-loading/loading-managed.md +++ b/docs/core/dependency-loading/loading-managed.md @@ -51,6 +51,7 @@ The following algorithm describes how the runtime loads a managed assembly. 3. For the other types of loads, the `active` loads the assembly in the following priority order: - Check its `cache-by-name`. + - If the `active` is the instance, check the instance's cache and run [managed assembly default probing](default-probing.md#managed-assembly-default-probing) logic. - Load from the specified path or raw assembly object. If an assembly is newly loaded, a reference is added to the `active` instance's `cache-by-name`. 4. In either case, if an assembly is newly loaded, then the event is raised. From c8ee833dbdc14b55c2274bb9b004a8ea19e7f0b3 Mon Sep 17 00:00:00 2001 From: Elinor Fung Date: Thu, 15 Jan 2026 11:31:52 -0800 Subject: [PATCH 3/5] Update docs/core/dependency-loading/loading-managed.md --- docs/core/dependency-loading/loading-managed.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/core/dependency-loading/loading-managed.md b/docs/core/dependency-loading/loading-managed.md index fa07035942131..f80ce65599b68 100644 --- a/docs/core/dependency-loading/loading-managed.md +++ b/docs/core/dependency-loading/loading-managed.md @@ -51,7 +51,7 @@ The following algorithm describes how the runtime loads a managed assembly. 3. For the other types of loads, the `active` loads the assembly in the following priority order: - Check its `cache-by-name`. - - If the `active` is the instance, check the instance's cache and run [managed assembly default probing](default-probing.md#managed-assembly-default-probing) logic. + - If the `active` is the instance, run [managed assembly default probing](default-probing.md#managed-assembly-default-probing) logic. - Load from the specified path or raw assembly object. If an assembly is newly loaded, a reference is added to the `active` instance's `cache-by-name`. 4. In either case, if an assembly is newly loaded, then the event is raised. From 019631d34269bccc69e385911ac70a0a3b96d845 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 15 Jan 2026 19:36:21 +0000 Subject: [PATCH 4/5] Update default-probing.md to clarify precedence of TPA and APP_PATHS Co-authored-by: elinor-fung <47805090+elinor-fung@users.noreply.github.com> --- docs/core/dependency-loading/default-probing.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/core/dependency-loading/default-probing.md b/docs/core/dependency-loading/default-probing.md index e3022eb63482e..864da921b52d7 100644 --- a/docs/core/dependency-loading/default-probing.md +++ b/docs/core/dependency-loading/default-probing.md @@ -64,6 +64,8 @@ When probing to locate a managed assembly, the in `TRUSTED_PLATFORM_ASSEMBLIES` (after removing file extensions). - Assembly files in `APP_PATHS` with common file extensions. +When loading in the default , assemblies found in `TRUSTED_PLATFORM_ASSEMBLIES` or `APP_PATHS` take precedence over a specified path or raw assembly object. For example, if you call or on the default 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. From 8a6e9ff2ea0590c30c65dd41ad7501a13bd79807 Mon Sep 17 00:00:00 2001 From: Elinor Fung Date: Thu, 15 Jan 2026 14:51:08 -0800 Subject: [PATCH 5/5] Update docs/core/dependency-loading/loading-managed.md Co-authored-by: Andy (Steve) De George <67293991+adegeo@users.noreply.github.com> --- docs/core/dependency-loading/loading-managed.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/core/dependency-loading/loading-managed.md b/docs/core/dependency-loading/loading-managed.md index f80ce65599b68..908394ad0b4f9 100644 --- a/docs/core/dependency-loading/loading-managed.md +++ b/docs/core/dependency-loading/loading-managed.md @@ -51,7 +51,7 @@ The following algorithm describes how the runtime loads a managed assembly. 3. For the other types of loads, the `active` loads the assembly in the following priority order: - Check its `cache-by-name`. - - If the `active` is the instance, run [managed assembly default probing](default-probing.md#managed-assembly-default-probing) logic. + - If the `active` is , 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` instance's `cache-by-name`. 4. In either case, if an assembly is newly loaded, then the event is raised.