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

wix burn extract -out extracts bundle contents without names when -outba is not specified #8142

Open
1 task done
ssrmm opened this issue Apr 16, 2024 · 1 comment
Open
1 task done
Labels
burn up for grabs No one volunteered to fix the issue. If you are interested, comment with "I want to fix this issue"

Comments

@ssrmm
Copy link

ssrmm commented Apr 16, 2024

WiX Version

5.0.0

.NET or MSBuild or Visual Studio Version

.NET SDK 7.0.315

HeatWave Version

N/A

Windows Version

Win11 22H2

Repro Repo

No response

Repro Steps

When calling wix burn extract with only the -out option, i.e. without the -outba. The extracted bundle contents are extracted under generic names a1, a2, etc. When -out and -outba are both specified, then the bundle contents are extracted with their proper names.

  1. Extract a Burn bundle
  2. Observe the created output files

Actual Result

For example when extracting the latest .NET Desktop Runtime installer:

$ wix.exe burn extract windowsdesktop-runtime-6.0.29-win-x64.exe -out out

produces the following directory structure:

└───out
        a0
        a1
        a2
        a3

These files are actually four MSIs for different parts of the runtime. but they cannot be distinguished easily.

While

$ wix.exe burn extract windowsdesktop-runtime-6.0.29-win-x64.exe -out out -outba outba

produces

├───out
│   └───WixAttachedContainer
│           dotnet-host-6.0.29-win-x64.msi
│           dotnet-hostfxr-6.0.29-win-x64.msi
│           dotnet-runtime-6.0.29-win-x64.msi
│           windowsdesktop-runtime-6.0.29-win-x64.msi
│
└───outba
    │   bg.png
    │   BootstrapperApplicationData.xml
    │   [...](omitted for brevity)

Note that in the second case the included MSI files in the out folder show their original file names and can easily be identified. Also note that there is an additional subfolder WixAttachedContainer now.

Expected Result

I would expect both command invocations to produce identical content in the out folder. Particularly I would like to have the proper file names no matter which way the command was invoked.

Whether the additional subfolder WixAttachedContainer exists or not does not make much of a difference for my use case, as long as it is consistent.

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).
@ssrmm ssrmm added the triage label Apr 16, 2024
@barnson
Copy link
Member

barnson commented Apr 30, 2024

One option is to add a new switch to extract both, so the manifest is available to provide the names for the files in the attached container (like WiX v3).

@barnson barnson added burn up for grabs No one volunteered to fix the issue. If you are interested, comment with "I want to fix this issue" and removed triage labels Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
burn up for grabs No one volunteered to fix the issue. If you are interested, comment with "I want to fix this issue"
Projects
None yet
Development

No branches or pull requests

2 participants