Storage Queue SDK 11 vs 12

[sowmyan soman]

Which service(blob, file, queue, table) does this issue concern?

Queue

Which version of the SDK was used?

Both 11 and 12

Which platform are you using? (ex: .NET Core 2.1)

.Net core 3.1

What problem was encountered?

When we send a message to queue (JSON string) using SDK 12 from a .Net core 3.1 console app and consuming it in another .Net Core console app using SDK 11 , it is failing to get the messages complaining about base64. Is it a known issue? if so is it documented anywhere?

How can we reproduce the problem in the simplest way?

Create two different .NET core console apps (3.1)
Use SDK 12 for sending the message to the queue ( JSON string)
Use SDK 11 for consuming the message from the queue
--> fails with base64 exception

Have you found a mitigation/solution?

Stick with one SDK version for both sending and consuming

[sowmyan soman]

Any comments??

[MScarno]

Hey sowsan,

As far as I know, by default on version 12, the messages are not encoded. This was not the case on previous version that was encoding in base64 by default.

You'll have to either base64encode on the v12 app before pushing or configure your message listener to stop decoding.
This might help :

• https://docs.microsoft.com/en-us/dotnet/api/system.convert.tobase64string?view=net-5.0
• https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.storage.queue.cloudqueue.encodemessage?view=azure-dotnet-legacy