-
-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support configuration for which field sets the version #182
Comments
When is |
Closing due to no response. |
This would address the four part version issue by making it configurable. |
AArnott
pushed a commit
that referenced
this issue
Feb 8, 2023
Bumps [Microsoft.CodeCoverage](https://github.com/microsoft/vstest) from 17.5.0-preview-20221109-01 to 17.5.0-preview-20221201-01. - [Release notes](https://github.com/microsoft/vstest/releases) - [Commits](https://github.com/microsoft/vstest/commits) --- updated-dependencies: - dependency-name: Microsoft.CodeCoverage dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be useful if there was a way to specify which of the NB.GV fields is used for the CloudBuildNumber, Version, PackageVersion and Version fields. It can default to what it does today, but there may be times when it's needed to override them.
Today, that means messing with MSBuild: https://github.com/onovotny/bc-csharp/blob/netstandard/scripts/setversion.csproj#L12-L19
If there's a .NET Core Global Tool (#181), that manipulation option isn't available.
The text was updated successfully, but these errors were encountered: