:::::::::::::: {.columns} ::: {.column width=”50%”}
Originally, each Azure team built their own .NET SDKs resulting in:
::: ::: {.column width=”50%”}
::: ::::::::::::::
::: notes
Each Azure team built their SDKs at different points in their product’s maturity
Language, operating system, and package manager support can vary wildly between SDKs
It’s also very difficult to discover new APIs as each API uses a different paradigm, naming scheme, GitHub repo structure, and even location on GitHub
:::
:::::::::::::: {.columns} ::: {.column width=”50%”}
::: ::: {.column width=”50%”}
The new Azure SDK introduces common guidelines that is designed to provide:
::: ::::::::::::::
::: notes
This is the first step towards applying a common set of standards to all Azure SDKs
Having a common model, makes it easier for new Azure teams to create a discoverable and predictable SDK
Having a core framework in place makes it easier to add support for new languages, operating systems, and package managers in the future
:::
:::::::::::::: {.columns} ::: {.column width=”50%”}
::: ::: {.column width=”50%”}
::: ::::::::::::::
::: notes
The github.com/azure/azure-sdk repository contains releases, documentation, and guidelines for all of the other repositories
The .NET, JavaScript, Python, and Java repositories contain source code, samples, and documentation relevant to that language
Each language repository contains SDK source code to access multiple Azure services in a predictable and consistent manner
:::
:::::::::::::: {.columns} ::: {.column width=”50%”}
::: ::: {.column width=”50%”}
::: ::::::::::::::
::: notes
The underlying guidelines and processes made it easier to add new languages
Each language supports a growing amount of Azure services
:::
::: notes
:::
Developer productivity is the core objective. The overall guidelines and each individual SDK is built around these paradigms:
::: notes
Building SDKs that model these paradigms can help increase developer productivity across all of Azure.
The paradigms are a core part of the underlying guidelines that are used to design each individual SDK.
Many existing SDKs required some rework to implement all five paradigms.
:::
using Microsoft.Azure.Storage;
using Microsoft.Azure.Storage.Blob;
string connectionString = "UseDevelopmentStorage=true";
CloudStorageAccount account = CloudStorageAccount.Parse(connectionString);
CloudBlobClient client = account.CreateCloudBlobClient();
::: notes
NuGet Package: Microsoft.Azure.Storage.Blob
:::
CloudBlobContainer container = client.GetContainerReference("files");
container.CreateIfNotExists();
::: notes
To get a client, you need to create CloudStorageAccount and CloudBlobClient instances
API calls inconsistently support synchronous and asynchronous operations
:::
using Azure.Storage.Blobs;
string connectionString = "UseDevelopmentStorage=true";
BlobServiceClient client = new BlobServiceClient(connectionString);
::: notes
NuGet Package: Azure.Storage.Blobs
:::
BlobContainerClient container = client.GetBlobContainerClient("files");
await container.CreateIfNotExistsAsync();
::: notes
The new SDK supports both synchronous and asynchronous API calls consistently
The SDK also renames the classes to be consistent across languages while respecting each individual languages’ idiomatic standards
:::
::: notes
Prerequisites: Ensure you have .NET 5 or higher installed.
Install the Preview.CSharp.Templates project template package from NuGet:
dotnet new --install Preview.CSharp.Templates
Initialize an empty top-level program using the dotnet CLI:
dotnet new script-empty
Install the Azure.Storage.Blobs package from NPM:
dotnet add package Azure.Storage.Blobs
Create a using directive for the Azure.Storage.Blobs namespace:
using Azure.Storage.Blobs;
Create a variable named connectionString of type string with a value of “UseDevelopmentStorage=true”:
string connectionString = "UseDevelopmentStorage=true";
Create a variable named client of type BlobServiceClient that stores the result of invoking the constructor of the BlobServiceClient class passing in the connectionString variable as a parameter:
BlobServiceClient client = new BlobServiceClient(connectionString);
Create a variable named container of type BlobContainerClient that stores the result of invoking the GetBlobContainerClient method of the client variable passing in the value “files” as a parameter:
BlobContainerClient container = client.GetBlobContainerClient("files");
Asynchronously invoke the CreateIfNotExistsAsync method of the container variable:
await container.CreateIfNotExistsAsync();
Save your changes to the Program.cs file.
Start the Azurite emulator using either the option on the status bar or the Azurite: Start
command in the Command Palette.
In the Activity Bar, navigate to the Azure option.
In the document tree within the Azure pane, expand the following nodes: Storage => Attached Storage => Local Emulator => Blob Containers.
Open a new terminal and run the .NET application:
dotnet run
Back in the Azure pane, open the context menu for the Blob Containers node and then select Refresh.
:::