Versioning NuGet packages in a continuous delivery world: part 1

This post introduces a strategy for versioning NuGet packages in a continuous delivery world, addressing the tension between Semantic Versioning (SemVer) and the need for unique version numbers for each CI build. It explains how to use SemVer's prerelease labels to create versioned CI packages (e.g., 1.0.0-ci-YYYYMMDD-HHMMSS) and outlines a process using Visual Studio Team Services (VSTS) builds with NuGet Packager and Publisher tasks to automate this. It also clarifies that NuGet.org is for released packages, not CI builds.