Masstransit Azure Service Bus message inheritance

[codebrainr]

Hi,
after reading the latest topics about publishing using ASB as Transport, I saw that
it was necessary to publish specifying directly in the generic the interface and in message parameter the message as a class.
I saw @Chris you replied ASB transport was not able to apply properly message inheritance,
is this still in this way?

Thanks

[Chris Patterson]

yes, until 4.0 this is the way it works.

--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.
To post to this group, send email to masstransit-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/81919e7f-721c-4b31-9368-b30a4921b778%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[codebrainr]

Thanks Chris.

On Thursday, August 31, 2017 at 10:23:11 PM UTC+2, Chris Patterson wrote:

yes, until 4.0 this is the way it works.

On Thu, Aug 31, 2017 at 12:24 PM, codebrainr <manuel....@gmail.com> wrote:

Hi,
after reading the latest topics about publishing using ASB as Transport, I saw that
it was necessary to publish specifying directly in the generic the interface and in message parameter the message as a class.
I saw @Chris you replied ASB transport was not able to apply properly message inheritance,
is this still in this way?

Thanks

--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.

To post to this group, send email to masstrans...@googlegroups.com.

[Shane Holder]

I was trying to understand this restriction, and put together the following console app.

https://pastebin.com/WjMKPKJg

There is a concrete class, which implements an interface and that interface implements 2 other interfaces.  Handlers are created for all 3 interfaces, and each handler is called so what exactly is the restriction?

MassTransit 3.5

On Thursday, August 31, 2017 at 3:23:11 PM UTC-5, Chris Patterson wrote:

yes, until 4.0 this is the way it works.

On Thu, Aug 31, 2017 at 12:24 PM, codebrainr <manuel....@gmail.com> wrote:

Hi,
after reading the latest topics about publishing using ASB as Transport, I saw that
it was necessary to publish specifying directly in the generic the interface and in message parameter the message as a class.
I saw @Chris you replied ASB transport was not able to apply properly message inheritance,
is this still in this way?

Thanks

--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.

To post to this group, send email to masstrans...@googlegroups.com.