This release removes all scanning around behaviors, stream behaviors, and pre/post processors. That proved too problematic so you MUST register each of these explicitly with the appropriate registration methods inside AddMediatR. This also ensures that the order of behaviors and pre/post processors reflects the explicit order of registration.

This is a pretty big release, with a number of breaking changes. * Release Notes * Migration Guide Breaking changes include: * Depending directly on IServiceProvider to resolve services * Making "void" request handlers return Task instead of Unit * IRequest does not inherit IRequest<Unit> instead IBaseRequest * Consolidating the MediatR.

I've been pointed at this post from various sources, and I thought I'd take the time to address the criticisms one by one. Not because I personally care too much, MediatR evolved over many years to solve the problems my teams faced, but since others seem

An issue I see come up quite frequently, much to the chagrin of DI container maintainers, are problems of complex generics edge cases and how they come up in MediatR. In fact, more than one container author has demanded some kind of recompense for the questions received and issues opened

MediatR 10.0.0 released today: * Release notes * Migration Guide * MediatR.Extensions.Microsoft.DependencyInjection release notes * NuGet This release adds support for IAsyncEnumerable<T> with separate types for this separate kind of request/response: * IStreamRequest<TResponse> * IStreamRequestHandler<in TRequest, TResponse> * IStreamPipelineBehavior<in TRequest,

A small release, from the release notes: This release contains a small, but breaking change. In order to provide a simpler interface, the IMediator interface is now split into two interfaces, a sender and publisher: public interface ISender { Task<TResponse> Send<TResponse>(IRequest<TResponse>

This release brings some (minor) breaking changes to the public API. First, we added a non-generic overload to Send on IMediator: public interface IMediator { Task<TResponse> Send<TResponse>(IRequest<TResponse> request, CancellationToken cancellationToken = default); + Task<object> Send(object request, CancellationToken cancellationToken = default)

Release notes: * MediatR 7.0.0 * MediatR.Extensions.Microsoft.DependencyInjection 7.0.0 It's a major release bump because of a breaking change in the API of the post-processor. Enjoy!

MediatR, a small library that implements the Mediator pattern, helps simplify scenarios when you want a simple in-memory request/response and notification implementation. Once you adopt its pattern, you'll often find many other related patterns start to show up - decorators, chains of responsibility, pattern matching, and more.

This release changes the default behavior of awaiting an enumerable of Task. Previous to this release, tasks where awaited using Task.WhenAll. This causes problems in a variety of environments and situations that expect sequential ordering. In this release, the default behavior for enumerables is to await in a foreach,

Another milestone for MediatR, I released 5.0 over the weekend. This release simplifies a number of interfaces and methods, but introduced some breaking changes along the way. The major change for MediatR in 5.0 is the combination of void requests to directly implement IRequest<Unit>. In