An abstract base class or Interface creates a new Azure Service BusTopic

When you add an interface or an abstract base class to a class that is used to publish data with MassTransit, it causes MassTransit to create an undesirable “extra” Service Bus Topic. For example:

This is fine:

public EventData {
 public string Text {get;set;]
}

There will be one Azure Service Bus Topic created called “EventData”.

However, if you add an interface:

public EventData : IHasText {
 public string Text {get;set;]
}

Then MassTransit will create an extra Topic called “IHasText”.

Is this by design? Is there a way to disable this behavior? I think it causes some quirky behavior when using temporary queues, but I’d have to verify (I’m using a named queue).

[joshmouch]

Confusing and complicated to implement? It definitely makes looking at the queues and topics more confusing. There’s no business-driven reason to ever publish something to an IHasText consumer, so it ends up just being extra clutter in Azure Service Bus.

[mburumaxwell]

Happy to see this resolved in the latest 7.0.4 release.