-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Windows Hosting Bundle should upgrade in place within a major.minor product band #7729
Labels
area-infrastructure
Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
feature-installers
Includes: Installers
Milestone
Comments
PR is almost complete. I'm just waiting on the final preview 3 build to drop |
joeloff
added a commit
that referenced
this issue
Mar 12, 2019
joeloff
added a commit
that referenced
this issue
Mar 19, 2019
joeloff
added a commit
that referenced
this issue
Mar 20, 2019
Fix for #7729 to ensure upgradable bundles
I have a few more tests to run, then I'll close it. Probably Monday if that's okay |
Sounds good. Monday @ noon we branch, but if it's just tests, just keep checking into master, and you're good to go. |
Testing looks good. I've done a couple of upgrades from the preview1 and 2 hosting bundles to the preview4 build. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-infrastructure
Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
feature-installers
Includes: Installers
When I install a new patch version of the hosting bundle, old patch versions with the same major and minor versions should be uninstalled. For example, installing
3.0.1
should uninstall3.0.0
.This is part of implementing in-place upgrade across Windows .NET Core installers: https://github.com/dotnet/core-setup/issues/4188.
dotnet/installer#530 implements this for the .NET Core SDK bundle, and the same work is planned for the .NET Core Runtime bundle.
@natemcmaster @joeloff
The text was updated successfully, but these errors were encountered: