Skip to main content

MediatR and StructureMap–Using Generic NotificationHandlers.

One of our application is using a CQRS approach in combination with MediatR and StructureMap. Part of the application is rather straightforward and to avoid a lot of boilerplate code we would like to use a NotificationHandler that could handle generic events. Here is the code we had written:

public class CreatedEntityEvent<TEntity> : EntityEvent<TEntity> where TEntity : Entity
{
public override string ToString() => $"{nameof(TEntity)} with id '{Id}' created.";
}
public class UpdatedEntityEvent<TEntity> : EntityEvent<TEntity> where TEntity : Entity
{
public override string ToString() => $"{nameof(TEntity)} with id '{Id}' updated.";
}
public class DeletedEntityEvent<TEntity> : EntityEvent<TEntity> where TEntity : Entity
{
public override string ToString() => $"{nameof(TEntity)} with id '{Id}' deleted.";
}
public abstract class EntityEvent : INotification
{
public Guid Id { get; set; }
}
public abstract class EntityEvent<T> : EntityEvent
{
}
view raw EntityEvent.cs hosted with ❤ by GitHub
public class NotificationHandler<TEntity> : INotificationHandler<EntityEvent<TEntity>>
{
public Task Handle(EntityEvent<TEntity> notification, CancellationToken cancellationToken)
{
//Implementation removed
}
}

However when we tried to register this using StructureMap nothing happened resulting in no event that was picked up by the NotificationHandler. Here is the registration code we had:

var registry = new Registry();
registry
.For<IMediator>().Use<Mediator>();
registry.For<SingleInstanceFactory>().Use<SingleInstanceFactory>(ctx => t => ctx.GetInstance(t));
registry.For<MultiInstanceFactory>().Use<MultiInstanceFactory>(ctx => (t) => ctx.GetAllInstances(t));
registry.Scan(scanner => {
scanner.AssemblyContainingType(this.GetType());
scanner.ConnectImplementationsToTypesClosing(typeof(IRequestHandler<>)); // Handlers with no response
scanner.ConnectImplementationsToTypesClosing(typeof(IRequestHandler<,>)); // Handlers with a response
scanner.ConnectImplementationsToTypesClosing(typeof(INotificationHandler<>));
});

The problem is that it is one level of generic too deep to handle by StructureMap, so StructureMap has no clue on how to close this open generic. To solve this problem we can create our own registry convention:

public class AddRequestHandlersWithGenericParametersToRegistry : IRegistrationConvention
{
public void ScanTypes(TypeSet types, Registry registry)
{
foreach (var concreteClass in types.FindTypes(TypeClassification.Concretes))
{
if (concreteClass.BaseType.Equals(typeof(Entity)))
{
RegisterType(registry, concreteClass, typeof(CreatedEntityEvent<>));
RegisterType(registry, concreteClass, typeof(UpdatedEntityEvent<>));
RegisterType(registry, concreteClass, typeof(DeletedEntityEvent<>));
}
}
}
private static void RegisterType(Registry registry, Type concreteClass, Type eventType)
{
var genericNotification = eventType.MakeGenericType(concreteClass);
var interfaceHandlerType = typeof(INotificationHandler<>).MakeGenericType(genericNotification);
var concreteHandlerType = typeof(NotificationHandler<>).MakeGenericType(concreteClass);
registry.For(interfaceHandlerType).Use(concreteHandlerType);
}
}

As a last step we have to apply this convention when configuring StructureMap:

registry.Scan(scanner => {
scanner.AssemblyContainingType(this.GetType());
scanner.ConnectImplementationsToTypesClosing(typeof(IRequestHandler<>)); // Handlers with no response
scanner.ConnectImplementationsToTypesClosing(typeof(IRequestHandler<,>)); // Handlers with a response
scanner.ConnectImplementationsToTypesClosing(typeof(INotificationHandler<>));
scanner.With(new AddRequestHandlersWithGenericParametersToRegistry());
});

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...