winui-packaging

Packages, signs, and publishes WinUI 3 apps as MSIX installers.

3|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill winui-packaging-jose-polanco-oxte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: winui-packaging
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/winui/sub-skills/winui-packaging
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill winui-packaging-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Preparing a WinUI 3 application for release involves certificate generation, code signing, MSIX packaging, and Microsoft Store submission, each with error-prone steps like publisher mismatches and untrusted certificates. This Skill provides the exact commands and workflows to handle the entire release pipeline correctly. ## Core Features & Use Cases - MSIX Packaging & Signing: Generate dev certificates, trust them, and package signed MSIX installers using the winapp CLI, including self-contained deployment and timestamped production signatures. - CI/CD Automation: Set up GitHub Actions pipelines that build, package, and upload MSIX artifacts on every push. - Microsoft Store Submission: Follow the release-driven msstore CLI pipeline for automated Store publishing, with Partner Center requirements like age ratings, screenshots, and privacy policies. - Use Case: You finished a WinUI 3 app and need to ship it. Use this Skill to generate a certificate, sign a self-contained MSIX, and wire up a GitHub Actions workflow that publishes to the Microsoft Store on each release. ## Quick Start Ask the assistant to package and sign your WinUI 3 Release build output into an MSIX installer using a generated development certificate.

Frequently Asked Questions about winui-packaging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I package a WinUI 3 app as an MSIX installer?

Build in Release configuration, then run winapp package with the build output directory and a certificate. The command stages the layout, generates resources.pri, creates the .msix, and signs it in one step.

How do I create and trust a code signing certificate for MSIX?

Run winapp cert generate --manifest to create devcert.pfx matching your manifest publisher, then run winapp cert install ./devcert.pfx from an elevated terminal to add it to the machine Trusted Root store.

Why does MSIX installation fail with a publisher mismatch error?

The certificate publisher must exactly match the Identity.Publisher field in Package.appxmanifest. Regenerate the certificate with winapp cert generate --manifest to auto-match the manifest value.

Can I automate MSIX packaging in GitHub Actions?

Yes. Use the microsoft/setup-WinAppCli action, build with dotnet build -c Release, then run winapp cert generate and winapp package with --quiet flags. Upload the resulting .msix with actions/upload-artifact.

Why does my MSIX signature become invalid over time?

Signatures expire with the certificate unless a timestamp is applied during signing. Re-sign with winapp package using the --timestamp flag pointing to a timestamp server such as http://timestamp.digicert.com.

When should I use self-contained deployment for a WinUI 3 app?

Use the --self-contained flag when target machines may not have the Windows App SDK runtime installed. It bundles the runtime into the package, producing a larger installer with no external runtime dependency.