Mike Minutillo

## Workaround - Replace the NSB created filters with correlation filters NServiceBus is designed to operate in a minimal access mode. With this in mind, it does not need to...

## Reported case: 82136 The user experienced throttling and opened a case with Microsoft after scaling out to 16 MUs for 24 hours without effect. Microsoft informed the user that...

We will create a test for this before we merge it. @timbussmann the CLA Assistant seems to be having trouble identifying your github account on this PR. Do you need...

@timbussmann I raised [another PR](https://github.com/Particular/NServiceBus/pull/6984) which will allow resolving the `ITransportAddressResolver` before the endpoint is started. It will still throw an exception if it is used early but this at...

Closed in favor of https://github.com/Particular/NServiceBus/pull/6984 which will allow early resolve as long the transport address resolver is not called before the endpoint is started.

Hi @evt-jonny We don't believe this is caused by assembly scanning. The receiver is able to handle the message as long as it has access to the message assembly containing...

I have been able to reproduce this problem exactly. If the concrete type is picked up by the assembly scanner, then it gets added to the Message Metadata Registry and...

@bbrandt One thing you may be able to do in the short-term is to create an NServiceBus behavior to rewrite the `EnclosedMessageTypesHeader` to something that can be loaded using `Type.GetType(..)`....

We are discussing internally how to handle this situation. This is caused by a very specific combination of features, specifically you need to be using: 1. Unobtrusive message conventions 2....

@evt-jonny @bbrandt given that the workaround has you unstuck, we have accepted this issue into our backlog and will figure out how to resolve it in a future release. Thank...