Package and deploy Windows apps overview
App packaging provides your application with a predictable installation, update, and servicing model on Windows. While WinUI apps are packaged by default, many other types of apps aren't. And adding package identity unlocks a wide range of Windows capabilities. Features that depend on package identity to function include background tasks, notifications, live tiles, custom context menu extensions, share targets, and other extensibility points. Packaging also helps ensure cleaner deployments, reliable updates, and streamlined distribution through channels such as the Microsoft Store and enterprise deployment tools.
When deploying apps that use the Windows App SDK, you can choose between framework-dependent and self-contained deployment models. Framework-dependent apps rely on the Windows App SDK runtime and/or framework package being installed on the user’s machine. In contrast, self-contained apps bundle the Windows App SDK dependencies directly with the application, ensuring the app carries everything it needs to run. The right model depends on your distribution scenario, update strategy, and how much control you want over the app’s footprint and dependencies.
Get started with packaging and deploying your Windows app
Packaging
Prepare your app for distribution by configuring how it’s packaged, installed, and updated.
Deployment
Learn how to deliver and manage the Windows App SDK with your app using framework or self-contained deployment options.
