I'm currently using "version\version.txt" with in each service Subfolder.
That file is edited by the Product Owner who owns "major.minor."
The build adds the 3rd position "build" as a counter that resets to 0 (for any change to version.txt)
Hi David,
We had version.txt for .NET Framework projects, but for Core we kept version in csproj files. I didn't like the option with the file, but it was "if it works...".
Since you have a non-tech person deciding on the version, maybe it would be good to move those values in some variables in Azure DevOps, so that it more PO-friendly :)
Ideally, you would use some simple option for versioning like github.com/adamralph/minver that could help if you see versioning as a pain point that just drains your time.
Thanks for sharing!
How did you manage versioning for each service?
I'm currently using "version\version.txt" with in each service Subfolder.
That file is edited by the Product Owner who owns "major.minor."
The build adds the 3rd position "build" as a counter that resets to 0 (for any change to version.txt)
Thoughts?
Hi David,
We had
version.txtfor .NET Framework projects, but for Core we kept version incsprojfiles. I didn't like the option with the file, but it was "if it works...".Since you have a non-tech person deciding on the version, maybe it would be good to move those values in some variables in Azure DevOps, so that it more PO-friendly :)
Ideally, you would use some simple option for versioning like github.com/adamralph/minver that could help if you see versioning as a pain point that just drains your time.
Oh, just one more option for versioning, similar to MinVer - Nerdbank.GitVersioning and a nice article bu Damien damienbod.com/2020/04/20/add-git-t...