-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Controlling version number (with a prerelease) when building #27527
Comments
I edited Version.props as below:
specifically editing When I build, I get
I would have expected How do I get |
Seems like the only way I can find to control this is from this as below?
|
@hounddog22030 This is not something I have tried to do. @dougbu @wtgodbe Any ideas here? |
Ok. If you've never tried doing it, maybe I'm barking up the wrong tree. Let me go back to my use case here: I am:
Because I cannot overwrite in the NuGet repository, I want to be able to do iterative builds as I get closer to the issue. e.g. Microsoft.EntityFrameworkCore.Tools.6.0.4-rollback-18.nupkg, Microsoft.EntityFrameworkCore.Tools.6.0.4-rollback-19.nupkg, Microsoft.EntityFrameworkCore.Tools.6.0.4-rollback-20.nupkg That's the tree I want to bark up. What would be the best way, using the current versioning infrastructure in EF Core (arcade?) to do the above. |
Local builds mostly ignore the prerelease settings in Eng/Versions.props. The way around it is to add a fake "official" build id to your build e.g. |
A PowerShell script to create the build parameter: $private:buildIdValue = [System.DateTime]::Now.ToString("yyyyMMdd.6")
$private:BuildId = "/p:OfficialBuildId=$buildIdValue"
Set-Clipboard -Value $BuildId
$BuildId Update the |
Something for the build docs? |
If I make a fork and build EF Core, I see that I should use build.sh/cmd.
Is there a method to
build -pack
with a pre-release version number, e.g. 6.0.2-with-my-new-feature?The text was updated successfully, but these errors were encountered: