Azure.ResourceManager.Hci

Azure Stack HCI Management client library for .NET

This package follows the new Azure SDK guidelines which provide a number of core capabilities that are shared amongst all Azure SDKs, including the intuitive Azure Identity library, an HTTP Pipeline with custom policies, error-handling, distributed tracing, and much more.

Getting started

Install the package

Install the Azure Stack HCI management library for .NET with NuGet:

dotnet add package Azure.ResourceManager.Hci --prerelease

Prerequisites

• You must have an Azure subscription

Authenticate the Client

To create an authenticated client and start interacting with Azure resources, please see the quickstart guide here

Key concepts

Key concepts of the Azure .NET SDK can be found here

Documentation

Documentation is available to help you learn how to use this package

• Quickstart
• API References
• Authentication

Examples

Code samples for using the management library for .NET can be found in the following locations

• .NET Management Library Code Samples

Troubleshooting

• File an issue via Github Issues
• Check previous questions or ask new ones on Stack Overflow using azure and .net tags.

Next steps

For more information on Azure SDK, please refer to this website

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 [email protected] with any additional questions or comments.