-
Notifications
You must be signed in to change notification settings - Fork 10.4k
[release/8.0] Chain runtime .Msi's instead of .Exe's in hosting bundle #56459
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
Conversation
<TargetPlatform>x64</TargetPlatform> | ||
<BundleNameProperty>DotNetRedistLtsInstallerx64</BundleNameProperty> | ||
<Version>$(MicrosoftNETCoreAppRuntimeVersion)</Version> | ||
</RuntimeInstallers> | ||
<RuntimeInstallers Include="$(DepsPath)dotnet-runtime-$(MicrosoftNETCoreAppRuntimeVersion)-win-x86.exe"> | ||
<RuntimeInstallers Include="$(DepsPath)dotnet-runtime-$(MicrosoftNETCoreAppRuntimeVersion)-win-x86.msi"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need two additional MSIs for runtime, similar to what we do in desktop. Both the host and hostfxr MSIs need to be included.
The test here would be that on a clean machine, you should be able to install the hosting bundle, then run dotnet --info
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also realized we don't need the ProductSearch anymore, removed those too
Permanent="yes" | ||
DetectCondition="SharedFxRedistProductVersion_arm64 = v$(var.SharedFxInstallerProductVersionarm64)"> | ||
</ExePackage> | ||
Permanent="yes"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think we need to remove the Permanent attribute too. When set, the MSI is marked as a system component so it won't remove it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have an internal build of this so I can look at a copy of the install?
https://dev.azure.com/dnceng/internal/_build/results?buildId=2488228&view=results is almost finished |
/backport to release/6.0 |
/backport to main |
Started backporting to release/6.0: https://github.com/dotnet/aspnetcore/actions/runs/9799873926 |
Started backporting to main: https://github.com/dotnet/aspnetcore/actions/runs/9799875112 |
@wtgodbe backporting to release/6.0 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: Chain runtime .msi's instead of .exe's in Hosting Bundle
.git/rebase-apply/patch:28: trailing whitespace.
</MsiPackage>
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M src/Installers/Windows/WindowsHostingBundle/DotNetCore.wxs
M src/Installers/Windows/WindowsHostingBundle/Product.targets
M src/Installers/Windows/WindowsHostingBundle/SharedFramework.wxs
M src/Installers/Windows/WindowsHostingBundle/WindowsHostingBundle.wixproj
Falling back to patching base and 3-way merge...
Auto-merging src/Installers/Windows/WindowsHostingBundle/WindowsHostingBundle.wixproj
CONFLICT (content): Merge conflict in src/Installers/Windows/WindowsHostingBundle/WindowsHostingBundle.wixproj
Auto-merging src/Installers/Windows/WindowsHostingBundle/SharedFramework.wxs
CONFLICT (content): Merge conflict in src/Installers/Windows/WindowsHostingBundle/SharedFramework.wxs
Auto-merging src/Installers/Windows/WindowsHostingBundle/Product.targets
CONFLICT (content): Merge conflict in src/Installers/Windows/WindowsHostingBundle/Product.targets
Auto-merging src/Installers/Windows/WindowsHostingBundle/DotNetCore.wxs
CONFLICT (content): Merge conflict in src/Installers/Windows/WindowsHostingBundle/DotNetCore.wxs
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Chain runtime .msi's instead of .exe's in Hosting Bundle
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
@wtgodbe an error occurred while backporting to release/6.0, please check the run log for details! Error: git am failed, most likely due to a merge conflict. |
Attempt to fix #55950
Test build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2482344&view=results
Test build w/ patch incremented: https://dev.azure.com/dnceng/internal/_build/results?buildId=2482415&view=results
Test build w/ patch decremented: https://dev.azure.com/dnceng/internal/_build/results?buildId=2483057&view=results