dotnet-msix

Automate MSIX package creation, signing, and distribution for .NET desktop applications.

10|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-msix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-msix
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/dotnet-msix
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-msix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the complex process of packaging .NET desktop applications into the MSIX format, enabling reliable deployment, signing, and submission to distribution channels like the Microsoft Store or direct sideloading.

Core Features & Use Cases

  • MSIX Creation: Generates MSIX packages from both single-project (.csproj) and Windows Application Packaging (WAP) projects.
  • Code Signing: Supports self-signed certificates for development and trusted CA certificates for production, including timestamping.
  • Distribution: Facilitates submission to the Microsoft Store, App Installer sideloading, and enterprise deployment via Intune or SCCM.
  • Auto-Update: Configures automatic updates using App Installer XML for seamless user experience.
  • MSIX Bundles: Creates .msixbundle files for multi-architecture support.
  • Use Case: Automate the entire build, sign, and package pipeline for your WinUI 3 application in CI/CD, ensuring it's ready for Microsoft Store submission or enterprise deployment.

Quick Start

Use the dotnet-msix skill to create a release MSIX package for the current project.

Frequently Asked Questions about dotnet-msix

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

FAQPage Schema
How do I package and sign a .NET desktop app as MSIX for deployment?

To package and sign a .NET app as MSIX, you can automate generation from .csproj or WAP projects, applying self-signed certificates for development or trusted CA certificates for production, including timestamping. This secures the application for reliable deployment.

Can I generate MSIX bundles for multi-architecture support in a CI/CD pipeline?

Yes, you can generate MSIX bundles for multi-architecture support in a CI/CD pipeline. The process creates .msixbundle files from your .NET desktop application, ensuring the packaged output covers multiple architectures for broader device compatibility.

What is the best way to submit a packaged WinUI 3 application to the Microsoft Store?

The best way to submit a packaged WinUI 3 application to the Microsoft Store is automating the build, sign, and package pipeline. This approach ensures the MSIX package meets Store submission requirements and is ready for enterprise deployment.

Does MSIX packaging support configuring automatic updates for sideloaded Windows apps?

MSIX packaging supports configuring automatic updates for sideloaded Windows apps by utilizing App Installer XML. This configuration enables seamless user experiences through App Installer sideloading and enterprise deployment via Intune or SCCM.

Do I need specific Windows SDK versions to create signed MSIX packages?

Yes, you need specific Windows SDK versions to create signed MSIX packages. Secure deployment and code signing with trusted CA or self-signed certificates require adherence to signing certificate requirements and the correct SDK environment setup.