[release/6.0] Make upgrade install new host first, then uninstall old #60317
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.
Backport of #60307 to release/6.0
Requires dotnet/arcade#8029
Customer Impact
Customers installing upgrades of .NET 6.0 observe the entry for dotnet will move to the end of the PATH variable, often resulting in x86 dotnet being first and winning.
Testing
Manual build of host and upgrade testing. I've tested upgrade scenarios where 5.0 x86 + x64 is installed. Upgrade to 6.0 x64 without the fix will move x64 PATH to end. Once fix is in place we don't move PATH entry.
Risk
Low. This doesn't change installer behavior like some of the other options we considered. The change is scoped to only the host MSI