About

Background & links

Please have a look at http://www.lionhack.com/2014/03/09/software-versioning-strategies/: this is a very good overview of the domain that explains .Net Version attributes, FileVersion attributes, version schemes, packages, etc. Of course, semantic versioning is a must: http://semver.org/

To discover NuGet:

• https://docs.microsoft.com/en-us/nuget/reference/package-versioning
• http://www.xavierdecoster.com/semantic-versioning-auto-incremented-nuget-package-versions
• NuGet - Top 10 NuGet (Anti-) Patterns: https://msdn.microsoft.com/en-us/magazine/jj851071.aspx
• http://haacked.com/archive/2011/10/24/semver-nuget-nightly-builds.aspx/ (even if it’s an old post, the discussion below the post is interesting)

About Git branches and workflow, read http://nvie.com/posts/a-successful-git-branching-model/.

You should also have a look at https://github.com/ParticularLabs/GitVersion/ that pursue the same goal as SimpleGitVersion but differently (it does not use CSemVer and relies on your Git flow).

Many thanks to our dependencies!

SimpleGitVersion.Core only depends on https://github.com/libgit2/libgit2sharp to interact with Git repository.

Development only dependencies are https://github.com/brutaldev/StrongNameSigner to automatically strong sign LibGit2Sharp during build and https://www.nuget.org/packages/ilmerge to merge LibGit2Sharp into SimpleGitVersion.Core.

SGV-Net solution uses NUnit, CodeCake (https://github.com/SimpleGitVersion/CodeCake) and SimpleGitVersionTask (its previous version) to manage its own version and build chain.