---
name: publish-extension
description: Guide for distributing your Command Palette extension through the Microsoft Store, WinGet, or both.
---

# publish-extension

Guide for distributing your Command Palette extension through the Microsoft Store, WinGet, or both.

# publish-extensionby microsoft
Guide for distributing your Command Palette extension through the Microsoft Store, WinGet, or both.

`npx skills add https://github.com/microsoft/powertoys --skill publish-extension`Download ZIPGitHub

## Publish Your Command Palette Extension

Guide for distributing your Command Palette extension through the Microsoft Store, WinGet, or both.

## When to Use This Skill

* Publishing your extension to the Microsoft Store

* Submitting your extension to WinGet for `winget install` discovery

* Setting up GitHub Actions to automate builds and releases

* Creating MSIX packages for Store submission

* Creating EXE installers for WinGet submission

## Publishing Options

ChannelPackage FormatDiscoveryAuto-UpdatesMicrosoft StoreMSIX bundleStore app, `ms-windows-store://` linkYesWinGetEXE installer`winget install`, CmdPal browseYes (via manifest)
Recommendation: Publish to both for maximum reach. WinGet enables direct discovery from within Command Palette.

## Workflows

### Microsoft Store Publishing

See store-publishing.md for the complete step-by-step guide.

Summary:

* Register for Partner Center

* Update `Package.appxmanifest` and `.csproj` with Partner Center identity

* Build MSIX for x64 and ARM64

* Create MSIX bundle

* Submit to Partner Center

### WinGet Publishing

See winget-publishing.md for the complete step-by-step guide.

Summary:

* Switch project to unpackaged mode

* Create Inno Setup installer script

* Build EXE installers

* Submit manifest via `wingetcreate new`

* Optionally automate with GitHub Actions

## Prerequisites

* Visual Studio with C# and WinUI workloads

* Partner Center account (for Store publishing)

* GitHub CLI (for WinGet publishing)

* WingetCreate — `winget install Microsoft.WingetCreate`

* Inno Setup (for WinGet EXE packaging)

## Important Notes

* Your extension's CLSID (the `[Guid("...")]` in your main .cs file) must be unique and consistent across all files

* WinGet manifests must include the `windows-commandpalette-extension` tag for CmdPal discovery

* MSIX packages require both x64 and ARM64 builds for Store submission

* WindowsAppSdk must be listed as a dependency in WinGet manifests

## More skills from microsoft
oss-growthby microsoftOSS growth hacker personapr-description-skillby microsoftTrigger this skill on any of the following intents:python-architectureby microsoftPython architect personasupply-chain-securityby microsoftSupply chain security expert personaskill-nameby microsoftDescription of what the skill does and when to use itwork-iterationsby microsoftList, create, and assign iterations for Azure DevOps projects and teams.djangoby microsoftBest practices for Django web development including models, views, templates, and testing.flaskby microsoftBest practices for Flask web development including routing, blueprints, and testing.

---

**Source**: https://github.com/microsoft/powertoys/tree/HEAD/src/modules/cmdpal/ExtensionTemplate/TemplateCmdPalExtension/.github/skills/publish-extension
**Author**: microsoft
**Discovered via**: mcpservers.org