Get Team City CI build and Release build set up for NuGet release.

[dazinator]

Set up Team City build.

CI Build --> Will use GitVersion for semver. Will update assembly infos with sem ver. Will create NuGet package release asset, using semver version approriate for NuGet. No unit tests to run currently.

Release Build (same build chain) --> Will nuget push the nuget package asset (from same build chain) to nuget.org. Will create release on GitHub, with auto generated release notes (using GitReleaseNotes) detailing issues closed (and PR's etc) since last release.

[dazinator]

Team City project setup.
There is a build chain.

"Continuous Integration" build is first in chain. Triggered automatically when changes detected in repo.

"Release Builds" are second in chain. They are triggered manually, and generate the release notes, and the release on GitHub (and upload the NuGet package attached to the GitHub release as a download)

"Publish to Nuget" builds are the last link in the build chain. Triggered manually, will push the NuGet package from the same build chain out to NuGet.org.

This means, it becomes very easy for me to Release to GitHub and Nuget - but I can do them independently if I wish - and the assets published will be from the same build.