[NETSDKE2E][WIX]After configuring the policy key for .NET 9 and set it to nextSession then sign out of the machine and sign back, the net9RC1 Hosting Bundle cannot be removed.

[v-ainigao]

Repro OS: windows11-x64 and arm64
Repro steps:
1.Adm run: REG ADD HKLM\SOFTWARE\Microsoft\.NET\9.0 /t REG_SZ /v RemovePreviousVersion /d nextSession
2.Install 9.0.0-rc.1.24452.1 Hosting Bundle
3.Install 9.0.100-rc.2.24468.15 Hosting Bundle
4.Verify that the RunOnce key exist and that it is targeting the RC1 bundle
Adm run: reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce /reg:32

5.Sign out of the machine and sign back in
6.Verify that RC1 is now removed

Expected Result:
The RC1 Hosting Bundle is now removed

Actual Result:
The net9RC1 Hosting Bundle cannot be removed


This is the captured log file.
vslogs.zip

[joeloff]

@wtgodbe I think I know what's going on. The hosting bundle is using its upgradecode as its provider key, so it ends up registering upgrades against itself.

I think we need to remove this line:

aspnetcore/src/Installers/Windows/WindowsHostingBundle/Bundle.wxs

Line 5 in 99135af

dep:ProviderKey="$(var.BundleProviderKey)">

We end up with

So when you try to remove the previous hosting bundle, it sees that there are multiple dependents registered, and simply removes the current bundles dependent, but doesn't do anything else

[170C:145C][2024-10-07T21:42:13]w209: Plan skipped removal of provider key: 45478415-b8e3-325c-bc58-50bf63fb515e because it is registered to a different bundle: {4d087993-b326-4a88-8e5e-02e73b16a00b}
[170C:145C][2024-10-07T21:42:13]w210: Plan skipped due to 1 remaining dependents

[joeloff]

And we should port this fix to main and release/8.0 for November servicing

[wtgodbe]

Thanks @joeloff - opened #58292 & backports to 9.0 to 8.0 (and moved this issue to aspnetcore)