[Discussion] New Azure Integration Packages in ASP.NET Core 5 #408

[analogrelay]

This is the discussion issue for aspnet/Announcements#408

ASP.NET Core currently includes three packages designed to integrate our components with Azure services. Specifically, the following three packages:

• Microsoft.Extensions.Configuration.AzureKeyVault, which integrates Azure KeyVault in to the Configuration system.
• Microsoft.AspNetCore.DataProtection.AzureKeyVault, which integrates Azure KeyVault into the ASP.NET Core Data Protection system.
• Microsoft.AspNetCore.DataProtection.AzureStorage, which integrates Azure Blob Storage into the ASP.NET Core Data Protection system.

The Azure SDK team is introducing brand new packages that provide the same extensions using the latest version of the Azure SDK. These packages will be maintained by the Azure SDK team at the Azure/azure-sdk-for-net repository. Moving these packages over to the Azure SDK team will allow that team to update them as the SDKs themselves are updated, rather than being tied to the .NET Core schedule.

If you are using any of the packages listed above, we suggest replacing them with the new packages:

• Microsoft.Extensions.Configuration.AzureKeyVault becomes Azure.Extensions.AspNetCore.Configuration.Secrets
• Microsoft.AspNetCore.DataProtection.AzureKeyVault becomes Azure.Extensions.AspNetCore.DataProtection.Keys
• Microsoft.AspNetCore.DataProtection.AzureStorage becomes Azure.Extensions.AspNetCore.DataProtection.Blobs

These new packages are supported on .NET Core 2.1 and 3.1 so you do not need to wait for 5.0 to update!

These are new packages that bring in a new version of the Azure SDK which includes breaking changes. The general usage patterns are the same as the existing packages, but some overloads and options may be different (in order to react to the changes to the underlying Azure SDK APIs).

The existing Microsoft. packages listed above will continue to be fully supported by the ASP.NET Core team for the lifetime of .NET Core 2.1 and 3.1. However, they will not be shipping in .NET 5. When upgrading your application to .NET 5, you will need to transition to the Azure. packages in order to be supported.

[juunas11]

Just wanna comment that I made a quick Core 3.1 app that uses the 2 data protection packages and it was really easy to plug them in :)
Here's a link to that: https://github.com/juunas11/Joonasw.AzureDataProtection/blob/0880cb95d08c220ce7fb8d754192da7f0ebe24bf/Joonasw.AzureDataProtection/Startup.cs#L43

Plugged DefaultAzureCredential to both and everything works really nicely locally.
I'll probably write up a blog post on using these 👍

[TechWatching]

What will happened to Microsoft.AspNetCore.AzureKeyVault.HostingStartup that is automatically added to a csproj when using "Connected Services" in Visual Studio 2019 ?

[analogrelay]

@TechWatching yep, we're working with that team to get a plan in place. For now it continues to use the legacy packages (which are still fully supported in .NET Core 2.1 and 3.1).

[tebeco]

Hello ;)

Is that normal ?
I mean if it's supposed to be already working for 2.1 and 3.x it should probably not look like this right ?

[analogrelay]

Looks like it got renamed/changed since the original preview. If you expand that notice, it has the details.

[tebeco]

@anurse
oO thanks a lot, I did not spotted that is was expandable, many thanks

Do you think it's possible to edit the links here for further lookup ?
#19570 (comment)

[analogrelay]

Should be, yeah. I still have permission since I posted the issue but perhaps @Pilchie should have someone on the team double check things since I'm no longer on the ASP.NET team.

[Pilchie]

I'm following up.

[Pilchie]

Updated the announcement issue, and the first comment on this issue with the packages, and removed the text about them being preview versions.

[tebeco]

thx a lot

[heaths]

So all references will be updated to the new packages? Was Microsoft.AspNetCore.All removed then? It accounts for 15.2% of our daily downloads of Microsoft.Azure.KeyVault, which we'd like to get on Azure.Security.KeyVault.Secrets instead. I can only find commits that remove references to it, unless I missed actual code clean up to remove the package for .NET 5.

If newer versions of the older packages for < .NET 5.0 will be updated, would it be feasible to update them to reference the new packages? The Azure SDK team can work with .NET on this to make sure the code calling into the new client libraries continues to work.

/cc @AlexGhiondea @pakrym

[Pilchie]

Microsoft.AspNetCore.All hasn't existed since .NET Core 2.2.

We cannot update packages for < 5.0, because it would be a breaking change. That's the whole reason we made the new packages in the first place.

[ghost]

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog clean. If you believe there is a concern related to the ASP.NET Core framework, which hasn't been addressed yet, please file a new issue.

This issue will be locked after 30 more days of inactivity. If you still wish to discuss this subject after then, please create a new issue!