microsoft/winappCli

microsoft/winappCli

Description: winapp, the Windows App Development CLI, is a single command-line interface for managing Windows SDKs, packaging, generating app identity, manifests, certificates, and using build tools with any app framework.

Language: C#

License: MIT

Stars: 1099

Forks: 54

Open issues: 38

Created: 2025-07-30T20:40:55Z

Pushed: 2026-06-10T03:31:01Z

Default branch: main

Fork: no

Archived: no

README:

winapp CLI

> [!IMPORTANT] > :warning: Status: Public Preview — The Windows App Development CLI (winapp CLI) is experimental and in active development. We'd love your feedback! Share your thoughts by creating an issue.

> [!NOTE] > The `main` branch contains work that is in active development. Documentation, features, and behavior here may differ from what is publicly released. For the latest stable version, see the latest release. To try the newest in-progress build, see [Install from latest build](#install-from-latest-build-main-branch) below.

Why? • Get Started • Installation • Usage • Docs • Feedback

The Windows App Development CLI (winapp CLI) is a single command-line interface for managing Windows SDKs, packaging, generating app identity, manifests, certificates, and using build tools with any app framework. This tool bridges the gap between cross-platform development and Windows-native capabilities.

Whether you're building with .NET/Win32, CMake, Electron, or Rust, this CLI gives you access to:

• Modern Windows APIs - Windows App SDK and Windows SDK with automatic setup and code generation
• Package Identity - Debug and test by adding package identity without full packaging in a snap
• MSIX Packaging - App packaging with signing and Store readiness
• Developer Tools - Manifests, certificates, assets, and build integration

Perfect for:

• Cross-platform developers using frameworks like Qt or Electron wanting native Windows features or targeting Windows
• Developers who love their current tools and want to build Windows apps from VS Code, or any other editor
• Developers crafting CI/CD pipelines to automate building apps for Windows

🤔 Why?

Many powerful Windows APIs require your app to have package identity, enabling you to leverage some of the OS components Windows offers, that you wouldn't otherwise have access to. With identity, your app gains access to user-first features like notifications, OS integration, and on-device AI.

Our goal is to support developers wherever they are, with the tools and frameworks they already use. Based on feedback from developers shipping cross-platform apps on Windows, we built this CLI to streamline integrating with the Windows developer platform - handling SDK setup, header generation, manifests, certificates, and packaging in just a few commands:

Without winapp CLI, setting up a project involves 12 manual steps—downloading SDKs, generating headers, creating manifests, and more. With the CLI, it's just 4 commands.

Few examples of what package identity and MSIX packaging unlocks:

• Interactive native notifications and notification management
• Integration with Windows Explorer, Taskbar, Share sheet, and other shell surfaces
• Protocol handlers (yourapp:// URIs)
• Web-to-app linking (yoursite.com opens your app)
• On-device AI (Local LLM, Text and Image AI APIs)
• Custom CLI commands via AppExecutionAlias
• Controlled access to camera, microphone, location, and other devices (with user consent)
• Background tasks (run when app is closed)
• File type associations (open .xyz files with your app)
• Startup tasks (launch at Windows login)
• App services (expose APIs to other apps)
• Clean install/uninstall & auto-updates

✏️ Get started

Checkout our getting started guides for step by step instructions of how to setup your environment, generate manifests, assets, and certificate, how to debug APIs that require package identity, and how to MSIX package your app.

Additional guides:

• [Packaging an EXE/CLI](/docs/guides/packaging-cli.md): step by step guide of packaging an existing exe/cli as MSIX

📦 Installation

WinGet

The easiest way to use the CLI is via WinGet (Windows Package Manager). In Terminal, simply run:

winget install Microsoft.winappcli --source winget

NPM

You can install the CLI for Electron projects via NPM:

npm install @microsoft/winappcli --save-dev

GitHub Actions / Azure DevOps

For CI/CD pipelines on GitHub Actions or Azure DevOps, use the `setup-WinAppCli` action to automatically install the CLI on your runners/agents.

Download Release Manually

[Download the latest build from GitHub Releases](https://github.com/microsoft/WinAppCli/releases/latest)

Install from latest build (main branch)

> [!CAUTION] > These builds are from the main branch and may include unreleased features, breaking changes, or experimental functionality. Use at your own risk.

Download the latest CI build artifacts directly (no GitHub login required):

| Artifact |…