Problem registering handler

[GonzaloMedinaMedina]

Hi! I'm sending a message with mediator from ProjectA and my handler is implemented in ProjectB, but when trying to send the message there are no handlers registered.
Is there a way to register handlers without knowing where are located?

Regards!

[jbogard]

Aren't they in the same application? The application should register the handlers for A and B.

[jbogard]

The application needs to do all the registrations. If these applications are in the same process it should be no problem at all, you'd just do something like:

services.AddMediatR(
   typeof(SomeTypeInA).Assembly,
   typeof(SomeTypeInB).Assembly,
   typeof(SomeTypeInC).Assembly,
   // etc
);

I don't understand why solutions can't reference each other, there's no technical reason why that can't happen. But that doesn't really matter here. If all of these projects/solutions are in the same application, and that application contains the single composition root for dependency injection, then you just have to register those handlers with the composition root. Not each project/solution with each other.

[GonzaloMedinaMedina]

There is a way to do these registers in a Mvc.net application?

[jbogard]

MVC 4/5? Yes, there's some docs in the wiki for registering directly against containers. You can also look at the samples folder, it has how to do different containers.

[GonzaloMedinaMedina]

Thank you but I found another problem, I'm using OwinStartup, there is a way to do this register through a IAppBuilder?
Because I can't register the service directly in the container like your screenshot.

[jbogard]

No idea, I've not used that in quite a long time. Here's what I found on StackOverflow:

https://stackoverflow.com/questions/19781970/how-to-use-di-container-when-owinstartup