skills.rest
microsoft
microsoftOFFICIAL
Explore all skills by this author →
Website𝕏@OpenAtMicrosoftGitHub

winapp-identity

Register sparse Windows package identity for desktop apps using Add-AppxPackage -ExternalLocation.

1.2k|68|Updated Jul 30, 2025
Search Tags:#debugging#packaging#manifest#identity#windows#msix
One-click install
npx skills add https://github.com/microsoft/winappCli --skill winapp-identity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: winapp-identity
Source: https://github.com/microsoft/winappCli/tree/main/.github/plugin/skills/winapp-cli/identity
Command: npx skills add https://github.com/microsoft/winappCli --skill winapp-identity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enable Windows package identity for desktop apps to access Windows APIs like push notifications, background tasks, share target, and startup tasks.

Core Features & Use Cases

  • Enables identity for debugging and development by registering a sparse MSIX identity for a standalone executable without copying files.
  • Supports Electron and other frameworks where the exe is separate from the build output; ideal for testing identity-related features.
  • Provides guidance on when to use it versus full MSIX packaging and how to re-run identity registration after changes.

Quick Start

Use winapp create-debug-identity <path-to-exe> to register a temporary identity for debugging.

Frequently Asked Questions about winapp-identity

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

FAQPage Schema
How do I enable Windows package identity for a desktop app during debugging?▼

To enable Windows package identity for debugging, register a sparse MSIX package using a temporary layout and Add-AppxPackage -ExternalLocation against your standalone executable without copying build files.

Can I get Windows package identity for an Electron app without full MSIX packaging?▼

Yes, you can register a temporary sparse identity for Electron apps where the exe is separate from build output, allowing you to test identity-requiring APIs without committing to full MSIX packaging.

What Windows APIs require package identity for desktop apps?▼

Windows APIs that require package identity for desktop apps include push notifications, background tasks, share target, and startup tasks, which are enabled by registering a sparse MSIX identity.

What's the best way to test startup task identity features for a standalone Windows executable?▼

The best way to test startup task identity for a standalone executable is registering a temporary sparse package that reads the manifest and applies identity using Add-AppxPackage -ExternalLocation.

Do I need to re-run identity registration after changing my desktop app manifest?▼

Yes, you must re-run the identity registration process after manifest changes to update the temporary sparse package layout and ensure your Windows identity-requiring APIs function correctly during development.

When should I use a sparse package identity versus full MSIX packaging for my Windows app?▼

Use a sparse package identity for development and debugging to test APIs without copying files, whereas full MSIX packaging is suited for final deployment and distribution of your Windows application.

Related Skills

Explore More Software Engineering Skills→
DotNetAgeDotNetAge
32

read_file

Reads a file and returns its content and byte count in JSON.

Community
Intermediate
beel-collabbeel-collab
1

winapp-cli

Automate Windows app packaging, signing, and manifest generation via CLI.

Community
Advanced
microsoftmicrosoft
1.2k

winapp-frameworks

Provide framework-specific Windows development guidance for Electron, .NET, C++, Rust, Flutter, and Tauri.

Official
Intermediate
microsoftmicrosoft
1.2k

winapp-package

Package built Windows app directories into MSIX installers with optional signing.

Official
Advanced