.NET Azure sdk resource manager - NuGet package: Stable release

Question

I'm planning to handle some Azure ARM code in .NET 6 and want to use Azure libraries.

I found that there are 2 NuGet packages (old and new) available:

1. Microsoft.Azure.Management.ResourceManager.Fluent

Ref: NuGet Gallery | Microsoft.Azure.Management.ResourceManager.Fluent 1.38.0 NuGet doc says that "This package is in low maintenance mode and being phased out. To use the latest Azure SDK for resource management, please see https://aka.ms/azsdk/dotnet/mgmt". This means that it package will not be supported in near future.

2. Azure.ResourceManager

Ref: NuGet Gallery | Azure.ResourceManager 1.0.0-beta.8 The official doc https://aka.ms/azsdk/dotnet/mgmt (referred from above NuGet suggestion) says that "Azure.ResourceManager.* packages are currently in Public Preview and may be subject to breaking changes in the future."

The former one is about to get deprecated and the latter one is still in beta release mode. Which package should be considered to be use for long term support application development. This needs to be used on production, so would going for beta release package recommended? Any expected stable release date for Azure.ResourceManager.* libraries?

Answer 1

The Azure SDK for .net has GAed 2 key libraries https://www.nuget.org/packages/Azure.ResourceManager/ and https://www.nuget.org/packages/Azure.ResourceManager.Resources/ Other azure services' SDK for .net will be available soon, we strongly recommend you start with the new version of Azure .NET SDK which start with name space Azure.Resource Meanwhile we are looking forward to hear our customer's feedback of the SDK experience, don't hesitate to raise your issue in our azure sdk .net github repo or directly reaching out to us via email

Answer 2

I would suggest you think about using the azure HTTP API that they support, but the problem is that a lot of endpoints is still in preview :D Don't worry to take beta SDKs for your solution coz it's gonna work fine. You might hit the problem only when you try to upgrade NuGet packages. So try to abstract this part and cover it whit tests :)