NServiceBus without spam my solution with IMessage / NServiceBus links

Has anyone found a reasonable way to use NServiceBus without having to implement this useless IMessage token interface for all messages?

In particular, when using DomainEvents, I absolutely would not want to associate my domains with a specific service bus implementation.

+3
source share
4 answers

The IMessage interface is required so that NServiceBus can automatically register these types in the serializer. When using domain events, it is not recommended to publish them directly on the bus - instead, the domain event handler will translate them to service level events (which inherit IMessage).

+1
source

, Udi NServiceBus 3.0. . sample writeup, github ( 2012 .). , POCO, .

+5

, , NSB, ILMerge NSB DLL. Dll NSB.

NSB , , , Udi

http://www.udidahan.com/2010/08/01/cautiously-merging-il/

0

Six months later, still nothing is said about this problem (fix / improve)

Summary of possible solutions: 1) ILMerge or .. 2) User dispatcher for personalized wrapped messages.

This is all due to the IMessage marker interface.

0
source

Source: https://habr.com/ru/post/1747713/


All Articles