Hi everyone,
We’ve just released NServiceBus.Transport.AzureServiceBus 2.0.2.
Improvements/Features
- #446 Add support for .NET 6 and .NET Core 3.1 in CommandLine app and tests.
Fixed bugs
- #454 Wire compatibility of messages sent by legacy transport broken in 2.0.1 release
How to know if you are affected
You are affected if you process messages sent by endpoints using the legacy NServiceBus.Azure.Transports.WindowsAzureServiceBus transport on endpoints using Azure Service Bus transport version 2.0.1.
You may not be affected if the endpoints using the legacy NServiceBus.Azure.Transports.WindowsAzureServiceBus transport have configured the BrokeredMessage body format to use the stream format.
Symptoms
Depending on the serializer used, a deserialization exception is thrown. Here is an example when using NewtonsoftSerializer:
NServiceBus.MessageDeserializationException: An error occurred while attempting to extract logical messages from incoming physical message 00000000-0000-0000-0000-000000000000 --->
Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: @. Path '', line 0, position 0.
When to upgrade
You should upgrade immediately if you are affected.
Where to get it
You can install the new version of NServiceBus.Transport.AzureServiceBus from NuGet.
To update an existing global tool installation, run dotnet tool update --global NServiceBus.Transport.AzureServiceBus.CommandLine.
With thanks,
The team in Particular
Please read our release policy for more details.