Is there a way to get all message/command handlers have been scanned/found by NServiceBus ? Some tricky solution (eg via ) will be suitable as well.
May I ask what is the use case for the information? Do you have a handler that is not registered correctly, and you try to understand what is happening?
Hi, a want to use this so to speak “internal registry” for some validation/logging purposes. I guess i could somehow get this handler list and avoid self-designed assembly scanning.
So the information is not easily accessible. Every endpoint scans the available DLLs in search of handlers. Those information is logged inside the diagnostics like in here
But the major problem is that every endpoint has only a fraction of the information: it knows which endpoint it has, and which it sends/publishes. Which only is a part of the system, so to get all handlers, one would have to analyze that information from every place.
You could have a look at this: https://github.com/ParticularLabs/RoutingVisualization
It is a tool to visualize endpoints and messages based on audits. In readme it describes where does it take the information, it could be something for you to use