azure-service-bus-dotnet | ️ .NET Standard client library for Azure Service Bus | Pub Sub library

I have a client written for some time ago that uses the old library and does call GetBody() to read the body when receiving messages.

Now I have the new client Microsoft.Azure.ServiceBus (sends messages) that as far as I understand always uses Stream.

So the old client just crashes as it expects string body type. I have found a lot of information on the opposite scenario (new reader, old writer), but cannot figure out how to make the new client send the data in required format.

Related links:

1. A stackoverflow answer
2. Interop extension to do the opposite (read an old message in the new client)

I keep getting MessageLockLostExceptions when processing messages.

• I am using Microsoft.Azure.ServiceBus 3.2.0 with .NET Core 2.1.
• I have a queue with LockDuration set to 30 seconds already containing a number of messages to be processed.
• I took the very basic message-receiving tutorial code from https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues#receive-messages-from-the-queue, which works fine.

Now I want to simulate a slightly longer running message processing task (but still well within LockDuration) by adding Task.Delay(10_000). But then I get a MessageLockLostException for exactly every 4th message.

This happens even if I set MaxAutoRenewDuration = TimeSpan.FromDays(30) and PrefetchCount = 0.

This is the message processing method, which I changed slightly to print out the remaining lock duration:

I downloaded the code from here: https://github.com/Azure/azure-service-bus-dotnet

and tried try to run the tests but am getting this: Message: System.TypeInitializationException : The type initializer for 'Microsoft.Azure.ServiceBus.UnitTests.TestUtility' threw an exception. ---- System.ArgumentException : Illegal connection string parameter name 'StsEndpoint' Parameter name: connectionString

I'm using on premise service bus version. Is this not supposed to be supported? This is the connection string I use:

Endpoint=sb://hostname.corp.domain.com/ServiceBusEapQANamespace;StsEndpoint=https://hostname.corp.domain.com:9355/ServiceBusEapQANamespace;RuntimePort=9354;ManagementPort=9355;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=bKnerepD9LBGHIVAM4nXJTw5kAAP5updfQYhH2gFG/o=

This same connection string works fine with other tools e.g. Service Bus Explorer

If I remove couple of the "unsupported" parameters and simplify my conn string to this: Endpoint=sb://hostname.corp.domain.com/ServiceBusEapQANamespace;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=bKnerepD9LBGHIVAM4nXJTw5kAAP5updfQYhH2gFG/o=

I get this error: Message: Microsoft.Azure.ServiceBus.MessagingEntityNotFoundException : None of the server sasl-mechanisms ([PLAIN,EXTERNAL]) are supported by the client (MSSBCBS).

I've opened an issue on the project's site for this as well

https://github.com/Azure/azure-service-bus-dotnet/issues/167

I want to send a message over Azure Service Bus from a .NET Core console app and receive it with in a .NET 4.6 console app. In .NET Core I'm using Azure's new service bus client for the sender which is not yet intended for production (according to their readme).

https://github.com/Azure/azure-service-bus-dotnet

I can send from .NET Core and receive with .NET Core easily enough using the samples. However when the .NET 4.6 app subscribes to the Topic and receives the same message the .NET 4.6 app throws this exception: