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.
Hi David,
We had
version.txt
for .NET Framework projects, but for Core we kept version incsproj
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.
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...