Skip to content
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

Bundle generates WIX8011: Failed to update resources in the bundle after upgrade to 5.0.0. #8114

Closed
1 task done
RichardJFoster opened this issue Apr 10, 2024 · 3 comments
Closed
1 task done
Labels

Comments

@RichardJFoster
Copy link

WiX Version

5.0.0

.NET or MSBuild or Visual Studio Version

MSBuild version 17.9.8+b34f75857 for .NET Framework

HeatWave Version

1.0.3.14

Windows Version

Win 11 23H2

Repro Repo

No response

Repro Steps

  1. Define a valid, working, bundle in Wix 4.X (we were on 4.0.5), which uses the WixStandardBootstrapperApplication and includes in the bundle chain the PackageGroupRef "NetFx472RedistAsPrereq", and an MSI PackageRef to a setup package from the same solution (e.g. <MsiPackage Id="MySetup" SourceFile="$(var.MySetup.TargetPath)" bal:DisplayInternalUICondition="WixBundleAction >= 6" />.
  2. Set the version for the bundle to the same value as the referenced package ( Version="!(bind.packageVersion.MySetup)").
  3. Update from Wix 4.0.5 to 5.0.0 and rebuild.

Actual Result

While the project generating the MSI appears to operate correctly, creation of the bootstrapper fails, apparently on the Bundle element itself, with the message error WIX8011: Failed to update resources in the bundle. Detail: Failed to save resource. Error 5.

Expected Result

I expected to see a successful bundle creation.

Acknowledgements

  • I acknowledge that this is a fully completed bug report. It is not a question or attempt to get help debugging my issue (because those should be sent to Discussions).
@barnson
Copy link
Member

barnson commented Apr 15, 2024

Please attach a binlog (msbuild -bl) so we can see detailed build info.

@RichardJFoster
Copy link
Author

Hopefully the attached binlog is helpful. Weirdly, while the error was seen in Visual Studio, it was not seen when running dotnet build. I also created what I hope will allow you to see the same issue in the repository at https://github.com/RichardJFoster/WiXRepro_8114. The initial commit closely resembles the specific scenario that is present in a current version of the software I am working on using WiX 4.0.5 where everything appears
to be OK. The second commit provides the equivalent changes I made when moving from 4.0.5 to 5.0.0 and shows the same result.

Please let me know if you need anything else.

MSBuild_binlog.zip

@barnson
Copy link
Member

barnson commented Apr 16, 2024

I couldn't reproduce the problem using MSBuild, dotnet build, or VS 17.9.6. WiX has automatic retry logic, so something's locking the file for an extended period of time. ProcMon should show you what's locking the file.

@barnson barnson closed this as not planned Won't fix, can't repro, duplicate, stale Apr 16, 2024
@barnson barnson added external and removed triage labels Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants