[Feature]: Create MSIX Bundles

[daniel-lerch]

Is your feature request related to a problem? Please describe.

When an app has been previously submitted as an .appxbundle or .msixbundle to Microsoft Store before, following submissions must use .appxbundle or .msixbundle as well. Currently, winapp CLI is only capable of creating MSIX files but developers must create their own bundles. That means locating your Windows SDK Tools folder, locating your MSIX files and bundling them manually.

Describe the solution you'd like

Option 1 (preferred)

Allow to pass multiple folders to winapp pack, e.g.
winapp pack bin\Release\net10.0\win-x64\publish bin\Release\net10.0\win-arm64\publish

I prefer this option because it does everything in one step and you get a file that you directly distribute or upload to Microsoft Store.

Option 2

Add an additional winapp bundle command, e.g.
winapp bundle MyApp_1.0.0.0_x64.msix MyApp_1.0.0.0_arm64.msix

Additional context

No response

[nmetulev]

Thanks for filing this - agree it's a real gap, and Option 1 is the right shape IMO

Design: extend winapp pack to accept multiple input folders. When you pass >1 folder, we:

• Reuse a single source manifest across all slices.
• Auto-detect each slice's ProcessorArchitecture from the EXE's PE header (we already do this for single-arch packs, so the manifest handling is essentially free).
• Validate Identity / Capabilities / Dependencies match across slices and fail fast with a readable diff if anything drifts.
• Produce <Name>_<Version>_<arches>.msixbundle.
• Sign the bundle (not the slices) if a cert is provided — per Microsoft's signing docs, the bundle signature covers the inner packages.

So the user only owns "give me N publish folders." Manifest, arch stamping, naming, and signing are all handled.

winapp pack bin\Release\net10.0\win-x64\publish bin\Release\net10.0\win-arm64\publish

Does this sounds like the right approach for what you need?

Quick proposed spec:
plan.md