VersionControl.ps1 "corrupts" version number

[danielniccoli]

File https://github.com/dsccommunity/DscWorkshop/blob/dev/DSC/Build/Tasks/VersionControl.ps1 causes a "corruption" in the version number. It replaces the PATCH version with the release version. This leads to a version number on the server, that is different than the version number in the configuration repository e.g., Repository: 1.1.3, Server 1.1.1.

According to the Semantic Versioning standard - which I assume is used here - the build number should be added as follows: MAJOR.MINOR.PATCH+BUILD.

[danielniccoli]

While writing a patch for it, I noticed that System.Version is used in VersionControl.ps1, which is structured as follows: MAJOR.MINOR.BUILD.REVISION

I think it would be a good idea to explain this in the documentation, so that when Azure DevOps is used, or any of the tools listed below, no changes are applied to the version number that the author didn't expect.

DscWorkshop/DSC/Build/Tasks/VersionControl.ps1

Line 3 in 0f25496

if ($env:BHBuildSystem -in 'VSTS', 'Azure Pipelines', 'AppVeyor') {