Sean Feldman

There's no story Jimmy. Either MSDN or another Azure subscription can be used to run on the real thing.

Either way works. Shared namespace is fine if you can "sandbox" development. I always advise to leverage MSDN subscription, unless you plan to use premium. Then you don't want create...

Layer of abstraction for code, yes. Running code w/o exercising client/broker, no. When working with ASB, you really should experience the "real thing".

@andrewbadera and when integration test (if you have one) against ASB is failing, what are you going to do locally? Wouldn't you switch back to ASB from whatever you were...

@andrewbadera don't get me wrong. I am **not** against layer of abstraction. I'm not a fan of replacing ASB with some other technology to emulate it.

> this isn't documented and does not provide a reasonable error message. If you don't mind, how did you find it out? Thank you.

> This is in our backlog, although we don't have timelines yet. The internal backlog is not visible and cannot be subscribed to receive updates. Please re-open this issue until...

This is a documentation/guidance not a bug issue. Please reopen and close when it's at least partially addressed. The question of impact of the topology on the performance is still...

This section[This section](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-performance-improvements?tabs=net-standard-sdk-2#compute-considerations) is the right step in the desired direction. Would be nice to expand on each on of those items on the list in the future.

2.5 years were worth waiting for this note 😂 > Mixing management and messaging operations in a transaction isn't supported. Jokes aside, appreciate finally closing this one with an action...