Arcade depends on the deprecated WindowsAzure.Storage package
See original GitHub issueThe WindowsAzure.Storage package is deprecated and should be replaced with Azure.Storage.Common
: https://www.nuget.org/packages/WindowsAzure.Storage
The library is currently used in couple of places in the repo and is undesirable for another reason: It brings in the entire netstandard1.x dependency graph (which includes vulnerable packages). By replacing it, we don’t need to manually bump vulnerable package versions anymore.
Issue Analytics
- State:
- Created 4 months ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
c# - How to replace Microsoft.WindowsAzure.Storage with ...
WindowsAzure.Storage is deprecated and the last version 9.3.3 was release on Nov 2018. Though it still works and not yet out of support,...
Read more >Usage of deprecated NuGet package: WindowsAzure. ...
This means that your application doesn't need to depend on the deprecated Storage SDK version to perform the file upload.
Read more >what is the replacement for Microsoft.Azure.Storage.Blob ...
To create a MigrationJob it requires to use Microsoft.Azure.Storage.Blob library and it is flagged as deprecated on nuget and flagged as legacy ...
Read more >WindowsAzure.Storage 9.3.3
This package has been deprecated as it is legacy and is no longer maintained. Additional Details. Please note, this package was officially ...
Read more >EPiServer.Azure uses deprecated package WindowsAzure ...
Hi, EPiServer.Azure uses package WindowsAzure.Storage which is deprecated. WindowsAzure.Storage is now (>1 year ago) splited into multiple packages, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We (dotnet/runtime, dotnet/corefx, dotnet/coreclr and dotnet/core-setup) don’t use these tools anymore. I don’t know the history behind them but I would be surprised if they are still used. Based on https://github.com/dotnet/arcade/pull/289 it sounds like those were used for the mirrored folders between the repos. We don’t do that anymore.
cc @ericstj
The only project I see using it is https://github.com/dotnet/arcade/blob/main/src/Microsoft.DotNet.GitSync.CommitManager/Microsoft.DotNet.GitSync.CommitManager.csproj#L19
I don’t believe this tool is maintained by dnceng as it was brought in from buildtools by corefx folks. The tool is not published anywhere. The fact that the only changes we have seen in this area are playing whac-a-mole with component governance, and that it was related to the old maestro in the old corefx world makes me think this code should be deleted along with the other project mentioned in https://github.com/dotnet/arcade/blob/main/Documentation/GitSyncTools.md