Just a small PR to update the Azure Storage Blob package to 11.1.0.
The current Azure Storage Blob version 9.4.2 depends on Microsoft.Azure.KeyVault.Core 1.0.0, which gives us this warning when compiling apps that depend on this project:
warning NU1701: Package 'Microsoft.Azure.KeyVault.Core 1.0.0' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework '.NETCoreApp,Version=v2.1'. This package may not be fully compatible with your project.
By updating the Blob package to 11.1.0, it depends on a later version of Azure.KeyVault that targets .NET Standard 2.0 properly, so the warning goes away.
There is a newer version of the Azure Storage Blob package that's very recently been released (v12), however this is more of a rewrite from the ground up, where the API has been completely redesigned. So in the meantime, I opted for this simpler stepping stone to 11.1.0 (which is still documented on the Azure docs).
Just a small PR to update the Azure Storage Blob package to 11.1.0.
The current Azure Storage Blob version 9.4.2 depends on Microsoft.Azure.KeyVault.Core 1.0.0, which gives us this warning when compiling apps that depend on this project:
warning NU1701: Package 'Microsoft.Azure.KeyVault.Core 1.0.0' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework '.NETCoreApp,Version=v2.1'. This package may not be fully compatible with your project.By updating the Blob package to 11.1.0, it depends on a later version of Azure.KeyVault that targets .NET Standard 2.0 properly, so the warning goes away.
There is a newer version of the Azure Storage Blob package that's very recently been released (v12), however this is more of a rewrite from the ground up, where the API has been completely redesigned. So in the meantime, I opted for this simpler stepping stone to 11.1.0 (which is still documented on the Azure docs).