Sean Feldman
Sean Feldman
@Rookian > However, currently 95% of the code Service Bus Explorer is using to communicate with queues and topics is using the oldest Service Bus SDK.
@Azure/azure-service-bus-write ping
No luck @nemakam. That block never executes.
@nemakam any updates on your end?
> > As of now, we don't know any scenario which is failing because of this, > do we? I have a use case where I want to go through...
@nemakam I'm at the point where I need to handle messages from old and new client and this issue become relevant again.
The old client is throwing `UnauthorizedAccessException`. For consistency, it would be good to throw the same exception as well.
@nemakam name wise, np. But the issue goes beyond that. Could you please comment on that? Thanks.
> This is a big breaking change The old client didn't support OnMessage API with multiple message, jus a single message. You can [receive batches](https://github.com/Azure/azure-service-bus-dotnet/blob/e5552e8cd2cb3072808ab306de164462bfd6c553/src/Microsoft.Azure.ServiceBus/Core/IMessageReceiver.cs#L68), just w/o MessageHandler. Exactly as...
Any [`IMessageReceiver`](https://github.com/Azure/azure-service-bus-dotnet/blob/e5552e8cd2cb3072808ab306de164462bfd6c553/src/Microsoft.Azure.ServiceBus/Core/IMessageReceiver.cs#L68) implementator.