This automates assembly and package versioning such that you can publish updates to your package as frequently as you want without worrying about ensuring you have unique versions or having to touch the source code to update the version number. Only when you explicitly want to change the major.minor part of the version do you have to make a source change, and even then, it's only in one place instead of potentially several files.
This includes the commit from #57 because both PRs have to add the Directory.Build.props file, so I would advise you consider and accept that PR before accepting this PR just to keep PR concerns isolated. If I were to isolate them here, you'd get a merge conflict for whichever PR you merge second.
This automates assembly and package versioning such that you can publish updates to your package as frequently as you want without worrying about ensuring you have unique versions or having to touch the source code to update the version number. Only when you explicitly want to change the major.minor part of the version do you have to make a source change, and even then, it's only in one place instead of potentially several files.
See https://github.com/aarnott/nerdbank.gitversioning for a full description of this feature.
This includes the commit from #57 because both PRs have to add the
Directory.Build.propsfile, so I would advise you consider and accept that PR before accepting this PR just to keep PR concerns isolated. If I were to isolate them here, you'd get a merge conflict for whichever PR you merge second.