You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 15, 2023. It is now read-only.
Use case: message handlers are in different projects (plugins), each having its own AddXXX method for single line configuration in the hosting project. The hosting project will not pass any assembly references to MediatR, as plugin registration is separated from infrastructure setup.
The text was updated successfully, but these errors were encountered:
Yes, each plugin has an AddXXX(this IServiceCollection) method, the host just composes the application by calling these registration methods, and then the plugins register their application parts and message handlers in the collection. Not that I can't write the same utility method (or copy it), but making the original public looks like a one-liner.
I don't really want to expand the public API in the root namespace. However, I'd be open to moving that assembly scanning stuff outside to a sub-namespace and making it public.
Use case: message handlers are in different projects (plugins), each having its own AddXXX method for single line configuration in the hosting project. The hosting project will not pass any assembly references to MediatR, as plugin registration is separated from infrastructure setup.
The text was updated successfully, but these errors were encountered: