winui-dev-workflow

Builds, runs, and diagnoses WinUI 3 apps using dotnet build and winapp run.

3|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill winui-dev-workflow-jose-polanco-oxte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: winui-dev-workflow
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/winui/sub-skills/winui-dev-workflow
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill winui-dev-workflow-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Building and launching packaged WinUI 3 apps involves platform detection, Developer Mode checks, and opaque crash errors like 0x8000FFFF that are hard to diagnose. This Skill automates the entire build-run-debug loop for WinUI 3 projects. ## Core Features & Use Cases - Automated Build & Run: The included BuildAndRun.ps1 script checks Developer Mode, auto-detects x64/ARM64 platform, builds with dotnet build or MSBuild, and launches via winapp run. - Crash Diagnosis: Uses winapp run --debug-output to perform WinUI stowed-exception triage, surfacing the real XAML error behind opaque E_FAIL crashes with a symbolicated native stack. - Error Reference: A table of common build and runtime errors (CS0234, XLS0414, 0x80073CF6, and more) with concrete fixes. - Use Case: You scaffold a new app with dotnet new winui-mvvm, then run BuildAndRun.ps1 to compile and launch it; when the app crashes on startup, the debug output reveals the actual XAML binding failure. ## Quick Start Ask the assistant to build and run the WinUI 3 project in the current directory using the BuildAndRun script and diagnose any errors that appear.

Frequently Asked Questions about winui-dev-workflow

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

FAQPage Schema
How do I build and run a WinUI 3 app from the command line?

Run the BuildAndRun.ps1 script in the project directory. It auto-detects the .csproj and platform (x64 or ARM64), builds with dotnet build, and launches the app with winapp run --debug-output.

How to diagnose a WinUI 3 app crash with error 0x8000FFFF?

Run the app under winapp run --debug-output, which is the BuildAndRun.ps1 default. It performs stowed-exception triage that surfaces the real XAML error behind the opaque E_FAIL plus a symbolicated native stack.

Why does my WinUI 3 app fail with Developer Mode not enabled?

Packaged WinUI 3 apps require Developer Mode to deploy and run. Enable it in Settings > System > For developers, then rerun the build script, which checks this prerequisite before building.

Can I run a packaged WinUI 3 exe directly instead of winapp run?

No. Running the packaged .exe directly causes silent exits or launch failures. Always use winapp run or the BuildAndRun.ps1 script, and never add WindowsPackageType None as a workaround.

What causes MSB3073 XamlCompiler.exe exited with code 1 in WinUI builds?

This is an old WindowsAppSDK XAML-compiler bug. Update the Microsoft.WindowsAppSDK NuGet package to version 2.1.3 or later, or 1.8 or later on the 1.x line.