CODEWITHSUNDEEP
c#azuresdk
Tomas Kubes
Tomas Kubes

Reputation: 25128

What are differences between .NET SDKs for Azure?

I have found two similar .NET libraries for Azure:

What is the difference? What is the intended use of them? Which one should I prefer for .NET/C#?

Upvotes: 2

Views: 135

Answers (1)

Ivan Glasenberg
Ivan Glasenberg

Reputation: 29985

First, azure-libraries-for-net is a management library, for managing Azure resources. Previously, it's a part of Azure SDK for .NET in Fluent branch. Since Sep 23, 2017, the Fluent branch is moved to azure-libraries-for-net, you can see here for moved information.

For what's the difference:

azure-libraries-for-net is called Fluent sdk(all the packages have a postfix .Fluent, see here), the code is easier to read and write. For example, if you want to create a virtual machine, you can just use one statement to create a virtual machine. Please refer to this article for usage of fluent sdk.

Azure SDK for .NET is called Generated SDK, and is not only for management, but also for the detailed operation, like upload a file to blob.

Here is an article which compares the Fluent sdk and Generated sdk for azure, it explains them very well.

Regarding Which one should I prefer for .NET/C#:

It depends on you. When using Fluent sdk, the code is easier to read and write. But sometimes, if the feature is not implemented / or in preview in Fluent sdk, you should choose Generated SDK.

Upvotes: 3

Related Questions