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. diff --git a/docs/core/dependency-loading/loading-managed.md b/docs/core/dependency-loading/loading-managed.md index 2d083a2f07ac4..908394ad0b4f9 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 , 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.