[BUG] Azure.Core depends on buggy version of System.Memory.Data

[KalaKala123]

Library name and version

Azure.Core 1.45.0

Describe the bug

Hi,
Azure.Core depends on System.Memory.Data >= 6.0.0 that has a bug in BinaryData.ToString().
When installing the latest version of Azure-relevant SDK such as Azure Storage blob SDK, that uses BinaryData type, it results in null reference exception.
The mitigation is explicitly installing a newer version of System.Memory.Data, that is not developer friendly.
Can you please upgrade the underlying version of System.Memory.Data to a newer version ?

BTW this is the bug in BinaryData.ToString that was fixed in newer versions
dotnet/runtime@a685d88

Expected behavior

Not getting null reference exception from BinaryData.ToString() when BinaryData is empty

Actual behavior

empty BinaryData throws null reference exception

Reproduction Steps

Install latest version of Azure.Core.
Then in your project write the following code:

var binaryData = new BinaryData(new byte[0]);

// throws Null ref exception
var x = binaryData.ToString()

Environment

No response

[jsquire]

Hi @KalaKala123. Thanks for reaching out and we regret that you're experiencing difficulties. Each of the Azure SDK packages are currently based on the 6.x line of BCL dependency packages. Unfortunately, there is no 6.x version of System.Memory.Data with a fix for that bug, as the .NET team has decided against patching it.

Our dependencies are managed very deliberately, as we have a need to maintain compatibility across a wide variety of runtime environments, some of which have strict requirements. For example, Azure Functions and Azure PowerShell both have built-in package sets with versions we cannot exceed. We are in the process of migrating to the 8.x versions to align with the current LTS, which requires extensive testing and is not likely to hit until at least April, more likely May.

Though we cannot make an immediate bump, the version of System.Memory.Data referenced by the Azure SDK packages does not constrain the version that you're able to use. By taking a direct reference to System.Memory.Data in your application, the version used by all of your dependencies will be hoisted to match. For example, taking a direct reference on v9.0.1 in your application would cause that version to be used by Azure.Core and the other Azure SDK packages that your application references, as you're asking.

The efforts for migration are tracked by the following. Since there is no value in redundant tracking here as well, I'm going to mark this as addressed.

• Tracking .NET 8 and 9 updates (#46639)
• Remove dependencies on deprecated packages in test projects (#47777)

[github-actions]

Hi @KalaKala123. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.