Neeraj Makam

@chuckb This seems to be an interesting one. However, don't think this is anything to do with our code. Should be a dotnet core on OSX bug. https://github.com/dotnet/coreclr should be...

@DavidBerg-MSFT Could I know if you are running into any issue? > Looking at the code for BuildSignature it will ignore the passed targetUri if the SharedAccessSignature field isn’t blank...

Could you try sending messages using old client with message body of type https://github.com/Azure/azure-service-bus-dotnet/blob/9d4d1ca430ab9b068537378c485005872065f874/src/Microsoft.Azure.ServiceBus/Amqp/AmqpMessageConverter.cs#L531-L546

I haven't had time to look into this task. There are few higher priority tasks that I'm looking into. As of now, we don't know any scenario which is failing...

Old client throws `System.UnauthorizedAccessException` . New client throws `Microsoft.Azure.ServiceBus.UnauthorizedException`. Wanted all known exceptions to extend from `ServiceBusException`. Hence the change

Yes. Its a very valid issue. That definitely will be fixed soon..

Like mentioned [here](https://github.com/Azure/azure-service-bus-dotnet/issues/52#issuecomment-275541006) , this would require AMQP transactions to be implemented first. Unfortunately, this would not make it to `1.0.0`.

This issue has been added to milestone `backlog`. Given that we haven't planned for this feature yet, it might not be right to assign `2.0` milestone for this issue yet.

@amit-kumar2 There is a slight difference in latency between sbmp and amqp. But it shouldn't be this much. Could you test the same code with amqp protocol using older `WindowsAzure.ServiceBus`...

@sameertotey Do you have a solution in mind?