Publishing to nuget

Publish all or specific subset

0. Ensure changelog is updated (can be done after GitHub release)
1. Create a GitHub release
2. Wait for tag do be built in Azure DevOps
   • Publish directly from devops
     1. create a "Release" based on the build (you must be logged in to se the option)
     2. Choose relevant option
        • "OpenRiaServices.All nuget" - publish all? nugets
        • "OpenRiaServices.Client" - Contains client parts and client code generation (EXCEPT T4 templates)
   • Manually upload to nuget.org
     1. Download the nuget packages from the build artifacts
     2. Login to nuget.org and upload the packages manually

Publish individual package

0. Ensure changelog is updated (can be done after GitHub release)
1. Create a GitHub release
2. Wait for tag do be built in Azure DevOps and download the nuget packages from the build artifacts
3. Edit the .nuspec file so that dependencies are the desired (latest published to nuget) Either: a. Open .nuget in 7-zip or similar editor and edit the .nuspec file "in place" b. Rename .nuget file to .zip,, extract, modify file, zip and renamve back to .nuget
4. Open the .nuget file in Nuget Package Explorer and verify that the dependencies and other metadata looks fine
5. Login to nuget.org and upload the package manually