Skip to content
This repository is intended for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs at https://docs.microsoft.com/en-us/dotnet/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-net.
C# HTML PowerShell TypeScript Shell Batchfile
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Add reviewers to double check API changes via CODEOWNERS (#8970) Dec 3, 2019
common/SmokeTests update smoke tests for October 2019 preview release (#8135) Nov 6, 2019
doc Update Using-Azure-TestFramework.md Dec 5, 2019
eng Generate 2019-09-01 policy operations (#8927) Dec 5, 2019
samples Fix Key Vault secrets doc references (#8647) Nov 6, 2019
sdk Make the AzureServiceTokenProvider mockable (#8464) Dec 5, 2019
tools Update impressions in all readmes (#8559) Nov 7, 2019
.editorconfig Update EditorConfig rule for public static fields (#7863) Oct 1, 2019
.gitattributes Change Delete and RecoverDeleted methods to LROs (#8175) Oct 18, 2019
.gitignore fix cpk tests (#8766) Nov 13, 2019
CONTRIBUTING.md Remove Client Badge (#8910) Nov 25, 2019
Directory.Build.props Fix build of mgmt libraries with new tools (#6554) Jun 13, 2019
Directory.Build.targets Nug tools (#6499) Jun 10, 2019
LICENSE.txt Updated LICENSE.txt Aug 7, 2015
NuGet.Config Generate public API listings and add up-to-date check for them (#8695) Nov 11, 2019
README.md Clean-up unified pipelines. (#8600) Nov 19, 2019
build.proj Update mgmt yml file (#6623) Jun 20, 2019
global.json Service Bus SDK Mar 12, 2019
mgmt.proj Fixing CR test projects. Updating build tools package. Disable non-wi… Jun 26, 2019
packages.md remove queue crypto library (#8837) Nov 23, 2019
swagger_to_sdk_config.json Update swagger_to_sdk_config.json (#8367) Oct 24, 2019

README.md

Azure SDK for .NET

This repository contains official .NET libraries for Azure services. You can find NuGet packages for these libraries here.

Getting started

To get started with a library, see the README.md file located in the library's project folder. You can find these library folders grouped by service in the /sdk directory.

For tutorials, samples, quick starts, and other documentation, go to Azure for .NET Developers.

Packages available

Client: November 2019 Releases

New wave of packages that we are announcing as GA and several that are currently releasing in preview. These libraries follow the Azure SDK Design Guidelines for .NET and share a number of core features such as HTTP retries, logging, transport protocols, authentication protocols, etc., so that once you learn how to use these features in one client library, you will know how to use them in other client libraries. You can learn about these shared features at Azure.Core.

These preview libraries can be easily identified by their folder, package, and namespaces names starting with 'Azure', e.g. Azure.Storage.Blobs.

The libraries released in the November 2019 GA release:

The libraries released in the November 2019 preview:

NOTE: If you need to ensure your code is ready for production use one of the stable, non-preview libraries.

Client: Previous Versions

Last stable versions of packages that are production-ready. These libraries provide similar functionalities to the preview packages, as they allow you to use and consume existing resources and interact with them, for example: upload a storage blob. Stable library directories typically contain 'Microsoft.Azure' in their names, e.g. 'Microsoft.Azure.KeyVault'. They might not implement the guidelines or have the same feature set as the Novemeber releases. They do however offer wider coverage of services.

Management

Libraries which enable you to provision specific server resources. They are directly mirroring Azure service's REST endpoints. Management library directories typically contain the word 'Management' in their names, e.g. 'Microsoft.Azure.Management.Storage'.

Need help?

Reporting security issues and security bugs

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.

Contributing

For details on contributing to this repository, see the contributing guide.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repositories using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Component Build Status
Management Libraries Build Status

Impressions

You can’t perform that action at this time.