winapp-package

When to use

Use this skill when:

• Creating an MSIX installer from a built app for distribution or testing
• Packaging any Windows app — GUI apps, console apps, CLI tools, services, or background processes
• Signing a package with a development or production certificate
• Bundling the Windows App SDK runtime for self-contained deployment

Prerequisites

Before packaging, you need:

1. Built app output in a folder (e.g., bin/Release/, dist/, build/)
2. Package.appxmanifest — from winapp init or winapp manifest generate
3. Certificate (optional) — devcert.pfx from winapp cert generate for signing

Usage

Basic packaging (unsigned)

# Package from build output — manifest auto-detected from current dir or input folder
winapp package ./bin/Release
 
# Specify manifest location explicitly
winapp package ./dist --manifest ./

Package and sign in one step

Generate certificate + package in one step

Self-contained deployment

Custom output path and name

What the command does

1. Locates Package.appxmanifest — looks in input folder, then current directory (or uses --manifest)
2. Copies manifest + assets into a staging layout alongside your app files
3. Discovers manifest-referenced files — any non-image file referenced in the manifest (e.g., AppExtension payloads like manifest.json, config files) is automatically copied from the manifest directory or input folder if missing from staging
4. Generates resources.pri — Package Resource Index for UWP-style resource lookup (skip with --skip-pri)
5. Runs makeappx pack — creates the .msix package file
6. Signs the package (if --cert provided) — calls signtool with your certificate

Output: a .msix file that can be installed on Windows via double-click or Add-AppxPackage.

Installing the MSIX for testing

Recommended workflow

1. Build your app (dotnet build, cmake --build, npm run make, etc.)
2. Package — winapp package <build-output> --cert ./devcert.pfx
3. Trust cert (first time) — winapp cert install ./devcert.pfx (admin)
4. Install — double-click the .msix or Add-AppxPackage ./myapp.msix
5. Test the installed app from the Start menu

Advanced: External content catalog

For sparse packages with AllowExternalContent, you may need a code integrity catalog:

Bundling multiple architectures

Create an MSIX bundle from multiple per-architecture build outputs:

How it works: When multiple input folders are passed, winapp package:

1. Detects the architecture of each folder's primary executable from its PE header
2. Resolves a manifest for each slice (see below)
3. Validates that all slices share the same Identity, Capabilities, and Dependencies
4. Packs each folder into an intermediate unsigned .msix
5. Bundles them into a single .msixbundle using makeappx bundle
6. Signs only the bundle (not individual slices) — the signature covers all packages inside

Manifest resolution: Each slice needs a manifest. Resolution order:

• --manifest <path> uses one manifest for all slices (architecture auto-stamped per folder)
• Per-folder Package.appxmanifest if present in the input folder
• Fallback to Package.appxmanifest in the current working directory

The ProcessorArchitecture is always force-set to the detected architecture per-slice. All other Identity fields must be consistent across slices.

Output: <Name>_<Version>_<arch1>_<arch2>.msixbundle (architectures sorted alphabetically).

Store submission: An unsigned bundle is valid for Store upload — Partner Center signs it with your reserved identity certificate. For sideloading, pass --cert or --generate-cert.

This hashes executables in the specified directories so Windows trusts them when running with sparse package identity.

CI/CD

GitHub Actions

Use the microsoft/setup-winapp action to install winapp on GitHub-hosted runners:

Tips for CI/CD pipelines:

• Use --quiet (or -q) to suppress progress output
• Use --if-exists skip with winapp cert generate to avoid regenerating existing certificates
• Store your PFX certificate as a repository secret and decode it in CI
• Use --use-defaults (or --no-prompt) with winapp init to avoid interactive prompts

Tips

• The package command aliases to pack — both work identically
• Package.appxmanifest Publisher must match the certificate publisher — use winapp cert generate --manifest to ensure they match
• Use --skip-pri if your app doesn't use Windows resource loading (e.g., most Electron/Rust/C++ apps without UWP resources)
• For framework-specific packaging paths (Electron, .NET, Rust, etc.), see the winapp-frameworks skill
• The --executable flag overrides the entry point in the manifest — useful when your exe name differs from what's in Package.appxmanifest
• For production distribution, use a certificate from a trusted CA and add --timestamp when signing with winapp sign

Sparse identity packages

To grant identity to an app distributed by an existing installer (not as MSIX), build an identity-only sparse package: pass a sparse appxmanifest.xml (one declaring <uap10:AllowExternalContent>true</uap10:AllowExternalContent> under <Properties>) to winapp pack instead of a folder.

The .msix contains only the manifest — binaries and assets are resolved from the external content location at runtime via Add-AppxPackage -ExternalLocation. If you pack a folder whose manifest declares AllowExternalContent, winapp pack warns about any assets/binaries found. See the Sparse Packaging Guide.

Related skills

• Need a manifest first? See winapp-manifest to generate Package.appxmanifest
• Need a certificate? See winapp-signing for certificate generation and management
• Having issues? See winapp-troubleshoot for a command selection flowchart and error solutions

Troubleshooting

CLI reference

Run winapp <command> --help for current command options, or winapp --cli-schema for the complete machine-readable command schema.