Skip to content

Updating .net core Assembly files with the generated version number in Azure DevOps #1783

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

Closed
makhaly opened this issue Aug 19, 2019 · 2 comments
Labels

Comments

@makhaly
Copy link

makhaly commented Aug 19, 2019

I am using Azure DevOps Pipelines to build my ASP.NET core application. recently i have added the Git Version Task between the Restore and Build .NET Core Tasks.

GitVersion is working perfect and generating a version number.
But after downloading the Artifacts i checked the Assembly version and file version and it has version 1.0.0.0 without applying the version number generated by the GitVersion Task.

I am using GitVersion Task Version 5

image

I am using the below configuration to force the use of the generated version in the Build Task
--configuration $(BuildConfiguration) -p:Version=$(GitVersion.SemVer)

image

@roryprimrose
Copy link

Hi @makhaly, this is probably a duplicate of #1611. Have a look at the powershell I use in that issue. That is how I got around this until GitVersion supports updating versions in the sdk project format.

@stale
Copy link

stale bot commented Jan 20, 2020

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 20, 2020
@stale stale bot closed this as completed Feb 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants