Microsoft.WindowsAppSDK.WinUI.CSharp.Templates 0.0.7-alpha

Windows App SDK WinUI 3 C# Templates

Official WinUI 3 project and item templates for the Windows App SDK, designed for use with the .NET CLI (dotnet new). This template pack provides the same starting points available in Visual Studio — blank apps, navigation views, MVVM scaffolding, tab-view shells, class libraries, unit test projects, and common WinUI UI items — right from the command line.

dotnet run launches the generated app with full MSIX package identity, so features that require it (notifications, background tasks, Windows AI APIs, etc.) work the same as they would in a Visual Studio F5 deploy.

Installation

dotnet new install Microsoft.WindowsAppSDK.WinUI.CSharp.Templates

Available Templates

Project Templates

Get below list via dotnet new list winui

Each winui-* short name also has a winui3-* alias (e.g. winui3-mvvm).

Reactor Templates (Experimental)

Microsoft.UI.Reactor is a declarative, React-style way to build WinUI 3 apps in pure C# — no XAML. These templates scaffold a runnable, single-project MSIX-packaged Reactor app whose UI mirrors the matching WinUI 3 XAML templates.

Get the list via dotnet new list reactor

Each also has a winui-reactor* alias (e.g. winui-reactor, winui-reactor-mvu) so they show up under dotnet new list winui alongside the other WinUI templates.

Reactor apps are packaged (single-project MSIX) and reference the Microsoft.UI.Reactor preview NuGet package. They require .NET 10 or later. Like the WinUI templates, they reference Microsoft.Windows.SDK.BuildTools.WinApp so dotnet run launches the app with full MSIX package identity. Pin a specific Reactor package version at scaffold time with --reactor-version, or the Windows App SDK version with --wasdk-version.

Item Templates

Item templates are context-aware and only surface when dotnet new is executed inside a WinUI project folder or when --project points to one.

Quick Start

Quickstart a new WinUI 3 APP

dotnet new winui -n MyApp
cd MyApp

# dotnet build
dotnet run

dotnet run registers a loose-layout MSIX, gives the app package identity, and launches it via AUMID activation — equivalent to F5 in Visual Studio.

Quickstart a new Reactor app

dotnet new reactor -n MyReactorApp
cd MyReactorApp
dotnet run

Reactor apps are pure C# (no XAML) and packaged (single-project MSIX), so dotnet run registers a loose-layout package and launches the app with full MSIX package identity — equivalent to F5 in Visual Studio. See the Reactor documentation to learn the component model, hooks, and layout system. Swap reactor for reactor-mvu, reactor-navview, or reactor-tabview to start from a richer shell.

Add items to an existing project

dotnet new winui-page         -n SettingsPage      --project .\MyApp.csproj
dotnet new winui-usercontrol  -n ProfileCard       --project .\MyApp.csproj
dotnet new winui-window       -n SecondaryWindow   --project .\MyApp.csproj
dotnet new winui-dialog       -n ConfirmDialog     --project .\MyApp.csproj

Choosing a Target Framework

Generated projects target net{N}.0-windows10.0.26100.0, where {N} is selected at scaffold time via --dotnet-version:

dotnet new winui --dotnet-version net8.0  -n MyApp
dotnet new winui --dotnet-version net9.0  -n MyApp
dotnet new winui --dotnet-version net10.0 -n MyApp

Supported choices: net8.0, net9.0, net10.0. If you omit --dotnet-version, most templates default to net10.0; winui-mvvm matches your installed .NET SDK. You can also edit <TargetFramework> in the generated .csproj afterward.

Customizing dotnet run behavior

Set any of these MSBuild properties inside a <PropertyGroup> in the generated .csproj to tweak how dotnet run launches the app:

These properties are provided by the Microsoft.Windows.SDK.BuildTools.WinApp NuGet package, which is referenced automatically by the project templates.

Prerequisites

• .NET SDK — net8.0, net9.0, or net10.0
• Windows 10 version 1809 (build 17763) or later
• Developer Mode enabled — required for dotnet run to register the loose-layout package. Settings → System → For developers → Developer Mode → On.

Resources

• Windows App SDK documentation
• WinUI 3 documentation
• Release notes
• File an issue

Contributing

This template pack is built from the WindowsAppSDK repository under dev/Templates/Dotnet/. The templates share the same XAML, code-behind, and project files as the Visual Studio templates under dev/Templates/Source/ProjectTemplates/ and dev/Templates/Source/ItemTemplates/, so there is only one copy to maintain.

Local Testing

1. Pack the templates:

   dotnet pack dev/Templates/Dotnet/WinAppSdk.CSharp.DotnetNewTemplates.csproj -c Release -o localpackages
   

2. Uninstall any previous version:

   dotnet new uninstall Microsoft.WindowsAppSDK.WinUI.CSharp.Templates
   

3. Install the local package:

   dotnet new install ./localpackages/Microsoft.WindowsAppSDK.WinUI.CSharp.Templates.<version>.nupkg
   

For an automated end-to-end run that scaffolds, builds, and (optionally) launches every template, use the included script:

.\dev\Templates\Dotnet\Test-DotnetNewTemplates.ps1                      # full run
.\dev\Templates\Dotnet\Test-DotnetNewTemplates.ps1 -SkipAppLaunch       # CI-friendly

Validation Checklist

• Run dotnet pack locally and dotnet new install to verify the local build.
• Run dotnet new list winui to review and confirm all templates are registered.
• Build generated projects for x64, x86, and ARM64 in Visual Studio or dotnet build.
• Test packaged deployments on Windows 10 version 1809 or later.