Skip to content

Conversation

wtgodbe
Copy link
Member

@wtgodbe wtgodbe commented Sep 22, 2021

Short-term fix for #36382. Add a wix project for the SharedFx bundles and reference that from the Hosting bundle, instead of the SharedFx .msi's. Also change the Hosting Bundle to ProjectReference SharedFrameworkBundle instead of having 2 ProjectReferences to SharedFrameworkLib - this ensures that by the time ResolveProjectReferences is done, the SharedFx .msi's are available so we can extract the Product Code from them & pass it along to the new wix project. Will need to backport this to servicing after I confirm it works with test builds.

I also removed BundleProviderKey from the SharedFx bundle after conversation with @joeloff to confirm it wasn't necessary.

CC @jamshedd

@wtgodbe wtgodbe requested review from joeloff and a team September 22, 2021 22:07
@wtgodbe wtgodbe requested a review from Pilchie as a code owner September 22, 2021 22:07
@ghost ghost added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Sep 22, 2021
Copy link
Contributor

@dougbu dougbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I defer to @joeloff for an actual approval

@wtgodbe
Copy link
Member Author

wtgodbe commented Sep 23, 2021

It works! Test build confirms that after installing Hosting bundle 5.0.n, shared framework bundle 5.0.n+1 will uninstall the older runtime that came with the hosting bundle.

@wtgodbe
Copy link
Member Author

wtgodbe commented Sep 23, 2021

/backport to release/5.0

@wtgodbe
Copy link
Member Author

wtgodbe commented Sep 23, 2021

/backport to release/6.0

@github-actions
Copy link
Contributor

Started backporting to release/5.0: https://github.com/dotnet/aspnetcore/actions/runs/1263979400

@wtgodbe
Copy link
Member Author

wtgodbe commented Sep 23, 2021

/backport to release/3.1

@github-actions
Copy link
Contributor

Started backporting to release/6.0: https://github.com/dotnet/aspnetcore/actions/runs/1263980012

@github-actions
Copy link
Contributor

Started backporting to release/3.1: https://github.com/dotnet/aspnetcore/actions/runs/1263980353

@github-actions
Copy link
Contributor

@wtgodbe backporting to release/3.1 failed, the patch most likely resulted in conflicts:

$ git am --3way --ignore-whitespace --keep-non-patch changes.patch

Applying: Chain SharedFx Bundle into Hosting Bundle instead of .msi
Applying: Fixup
Applying: Move stuff around
Using index info to reconstruct a base tree...
M	src/Installers/Windows/WindowsHostingBundle/Product.targets
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/Product.targets
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0003 Move stuff around
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

@jamshedd
Copy link
Member

It works! Test build confirms that after installing Hosting bundle 5.0.n, shared framework bundle 5.0.n+1 will uninstall the older runtime that came with the hosting bundle.

Hurray!

@wtgodbe
Copy link
Member Author

wtgodbe commented Sep 23, 2021

/backport to release/2.1

@github-actions
Copy link
Contributor

Started backporting to release/2.1: https://github.com/dotnet/aspnetcore/actions/runs/1263991368

@github-actions
Copy link
Contributor

@wtgodbe backporting to release/2.1 failed, the patch most likely resulted in conflicts:

$ git am --3way --ignore-whitespace --keep-non-patch changes.patch

Applying: Chain SharedFx Bundle into Hosting Bundle instead of .msi
Using index info to reconstruct a base tree...
M	src/Installers/Windows/SharedFrameworkBundle/Bundle.wxs
M	src/Installers/Windows/WindowsHostingBundle/Bundle.wxs
M	src/Installers/Windows/WindowsHostingBundle/Product.targets
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/Product.targets
Auto-merging src/Installers/Windows/WindowsHostingBundle/Bundle.wxs
Auto-merging src/Installers/Windows/SharedFrameworkBundle/Bundle.wxs
CONFLICT (content): Merge conflict in src/Installers/Windows/SharedFrameworkBundle/Bundle.wxs
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Chain SharedFx Bundle into Hosting Bundle instead of .msi
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

@wtgodbe wtgodbe merged commit ac0a387 into main Sep 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants