Azure Pipelines build and release pipeline

At present, we have a mix of build systems that I would like to unify.

1. Azure Pipelines for Linux, Windows and macOS.
2. Travis for Linux and macOS
3. Appveyor for Windows

I'd like to standardize around Azure Pipelines. At the moment, it's only doing a build for validation. I would like the build step to:

1. Create a nuget package (see AppVeyor's build configuration)
2. Upload that nuget package to Azure Artifacts

Then I'd like to have a separate release pipeline that will:

1. Take the nuget package from Azure Artifacts
2. Upload the nuget package to nuget.org

Commencez par le build de validation Azure Pipelines existant et la configuration de build d’AppVeyor, qui sont les points d’entrée nommés dans l’issue. Suivez la manière dont le package NuGet est créé et identifiez les étapes de publication vers Azure Artifacts et nuget.org. Le travail est terminé lorsque Azure Pipelines build et stocke le package, tandis qu’un pipeline de release distinct le publie sur nuget.org.