You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version 12.5 of Azure.Storage.Queues adds support for binary data, custom shapes and Base64 encoding, which enables the possibility to worth with BinaryData and encourages switching over to that instead of MessageText which we still use everywhere.
Due to our current use of MessageText rather than binary data, there are certain native integration scenarios that would currently just break. Using binary data would enable the transport to read the data no matter the formtting, and at least provide it for behaviors to massage into a shape that can be processed.
Version 12.5 of Azure.Storage.Queues adds support for binary data, custom shapes and Base64 encoding, which enables the possibility to worth with BinaryData and encourages switching over to that instead of MessageText which we still use everywhere.
Due to our current use of MessageText rather than binary data, there are certain native integration scenarios that would currently just break. Using binary data would enable the transport to read the data no matter the formtting, and at least provide it for behaviors to massage into a shape that can be processed.
Related to Particular/NServiceBus.DataBus.AzureBlobStorage#415
The text was updated successfully, but these errors were encountered: