diff --git a/docs/core/dependency-loading/loading-managed.md b/docs/core/dependency-loading/loading-managed.md index 73f5281109187..6b8518b1983cf 100644 --- a/docs/core/dependency-loading/loading-managed.md +++ b/docs/core/dependency-loading/loading-managed.md @@ -49,8 +49,8 @@ The following algorithm describes how the runtime loads a managed assembly. - Check its `cache-by-name`. - Call the function. - Check the 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 instance's `cache-by-name`. - - Raise the event for the active AssemblyLoadContext. - - Raise the event. + - Raise the 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 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` loads the assembly in the following priority order: