[release/6.0] Allow Hosting Bundle to be upgraded by MU#37967
Merged
wtgodbe merged 8 commits intorelease/6.0from Nov 5, 2021
Merged
[release/6.0] Allow Hosting Bundle to be upgraded by MU#37967wtgodbe merged 8 commits intorelease/6.0from
wtgodbe merged 8 commits intorelease/6.0from
Conversation
ghost
added
the
area-infrastructure
|
Hi @wtgodbe. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document. |
This was referenced Nov 1, 2021
|
Hi @wtgodbe. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge. To learn more about how to prepare a servicing PR click here. |
Member
Author
|
Approved by tactics |
joeloff
reviewed
Nov 4, 2021
joeloff
reviewed
Nov 4, 2021
| Key="Software\Microsoft\dotnet\host\options\$(var.MajorVersion).$(var.MinorVersion)" | ||
| Value="$(var.Option)" | ||
| Result="exists" | ||
| Variable="$(var.Option)_Should_Be_Set"/> |
Member
There was a problem hiding this comment.
Can we rename this to '$(var.Option)_Exists' - that's the convention we typically used for existence checks. Sorry I didn't catch this earlier. It also make the second search condition a bit more readable since right now we have to similarly named variables that differ by "S" and "s"
joeloff
approved these changes
Nov 4, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Customer Impact
Adds an .msi,
dotnet-hosting-options, which writes to the registry the value of the switches used when last installing the hosting bundle for a given Major.Minor version. Subsequent installs of that band of the hosting bundle will choose what the install in the following way:0for any switches not passed).0and write0to the registry for each switchTesting
Tested various scenarios with versions of the new hosting bundle across multiple Major.Minor.Patch versions, as well as how it interacts with previous Hosting Bundles without the Registry-writing behavior.
Risk
In December all customers who get this update thru MU will get a 1-time hit where, regardless of what they already had installed, the hosting bundle will install all components. We suspect most customers install everything anyways, and those who don't will be able to work around this by manually re-running the installer with whatever switches they passed the last time they installed the bundle manually. Additionally, there could be a scenario that we didn't think of (and therefore wasn't covered by our manual testing) that will break.