WinUI templates for dotnet new and VSIX by DinahK-2SO · Pull Request #6407 · microsoft/WindowsAppSDK

DinahK-2SO · 2026-04-16T07:55:36Z

This PR adds/updates the WinUI App templates:

Add WinUI templates for dotnet new
Add 2 new templates for Visual Studio:
- WinUI Navigation App
- WinUI TabView App
Add guidelines and scripts for local build

Copilot

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

…ty, and testing guidelines (#6217)

* Add pipelines * Update readme

* Adding TitleBar and .ico * Adding the ContentDialog ItemTemplate * Adding NavigationView template * Missed a csharp template and added * Push * Update WinAppSdk.CSharp.DotnetNewTemplates.csproj * Clean up navview project * Update dev/VSIX/ProjectTemplates/Desktop/CSharp/NavigationApp/Pages/HomePage.xaml.cs Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update dev/VSIX/ProjectTemplates/Desktop/CSharp/NavigationApp/Pages/AboutPage.xaml.cs Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update dev/VSIX/ProjectTemplates/Desktop/CSharp/NavigationApp/Pages/SettingsPage.xaml.cs Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update dev/VSIX/ProjectTemplates/Desktop/CSharp/NavigationApp/App.xaml.cs Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update dev/VSIX/ItemTemplates/Neutral/CSharp/ContentDialog/ContentDialog.xaml.cs Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update dev/VSIX/ProjectTemplates/Desktop/CSharp/NavigationApp/MainWindow.xaml.cs Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Add default case with exception to navigation switch statement (#6252) * Initial plan * Add default case throwing InvalidOperationException in navigation switch statement Co-authored-by: niels9001 <9866362+niels9001@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: niels9001 <9866362+niels9001@users.noreply.github.com> --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Co-authored-by: niels9001 <9866362+niels9001@users.noreply.github.com>

…hing

* Add missing item-content-dialog template for dotnet new The csproj referenced templates/item-content-dialog/ but the directory did not exist, which would cause dotnet pack to produce an incomplete package. Create the template.json, dotnetcli.host.json, and the XAML and code-behind files for a WinUI 3 ContentDialog item template. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add packaged template to NuGet template pack The templates/packaged/ directory existed with a full template.json and solution file but was never included in the csproj ItemGroups, so it would not ship in the NuGet package. Add the ItemGroup that packs the template config, solution, BlankApp, and WapProj sources. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update README with packaged and content-dialog templates The template table was missing the wasdk-packaged and wasdk-item-dialog entries. Add both so the README accurately documents all templates shipped in the pack. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add language and type tags to all template.json files Without the 'tags' property, 'dotnet new list' does not show the language column and template discoverability is reduced. Add tags.language=C# and tags.type (project, solution, or item) to every template. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add postActions for automatic NuGet restore After 'dotnet new' creates a project, the user currently has to manually run 'dotnet restore'. Add the standard NuGet restore post- action (actionId 210D431B) to the four project templates so packages are restored automatically. Item templates do not need this. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add Windows-only OS constraint to all templates WinUI 3 / Windows App SDK templates only work on Windows. Without the constraint, 'dotnet new list' shows them on Linux and macOS where they cannot build, leading to confusing errors. Add the os constraint so the templates are hidden on non-Windows hosts. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add description fields to template parameters The single-project, class-library, and unit-test templates were missing description fields on their user-facing parameters. The packaged template already had them. Add matching descriptions so 'dotnet new <template> --help' displays useful parameter documentation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add description fields to dotnetcli.host.json files The packaged template's host file already had descriptions but the single-project, class-library, unit-test, and item-blank-window host files did not. Add descriptions so 'dotnet new <template> --help' displays useful help text for every parameter. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add Copyright, license acceptance, and release notes to csproj The NuGet package was missing Copyright, PackageRequireLicenseAcceptance, and PackageReleaseNotes metadata. Add them for completeness and better presentation on NuGet feeds. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update default dotnetVersion from net8.0 to net9.0 .NET 9.0 is the current release. Update the default TFM across all four project templates and their dotnetcli.host.json description examples. Users can still override with --dotnet-version net8.0. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Use https:// for JSON schema URLs All template.json and dotnetcli.host.json files used http:// for the schema store URLs. Update to https:// for consistency and security. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Revert packaged template from dotnet new pack The wasdk-packaged template uses a WAP project (.wapproj) which the dotnet CLI does not understand, so it cannot be used with 'dotnet new'. Remove the packaged template ItemGroup from the csproj, remove it from the README, and restore its template.json and dotnetcli.host.json to their pre-modification state. This reverts the packaged-related portions of commits 31f65f2, b8c76b7, 80c1b8f, 63d5abf, ff0bc38, 7c03a19, and 4891155. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Use existing VS ContentDialog sources instead of hand-crafted copies The ContentDialog XAML and code-behind already exist at ItemTemplates/Neutral/CSharp/ContentDialog/. Link those files in the csproj instead of maintaining separate copies, matching the pattern used by the BlankWindow item template. This keeps a single source of truth and preserves the original button click handlers. Also update template.json sourceName and primaryOutputs to match the original filenames (ContentDialog, not ContentDialogItem), and remove the now-unnecessary Compile Remove directive. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Align packaged template config with other templates The previous revert restored the packaged template.json and dotnetcli.host.json to their original state, making them inconsistent with the rest of the templates. Re-apply the same improvements: add tags, constraints, postActions, update schema to https://, and default TFM to net9.0. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Remove templates/packaged/ directory The packaged template uses a WAP project (.wapproj) which the dotnet CLI does not support, so it is not included in the NuGet template pack. Remove the unused directory to avoid confusion. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update default dotnetVersion from net9.0 to net10.0 .NET 10.0 is the latest officially supported version. Update the default TFM and help text examples across all project templates. Users can still override with --dotnet-version net8.0 or net9.0. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Rename template shortNames from wasdk-* to winui3-* Use winui3- prefix instead of wasdk- since WinUI 3 is the product name users recognize, not the shipping vehicle (Windows App SDK). wasdk-single -> winui3 wasdk-classlib -> winui3-lib wasdk-unittest -> winui3-unittest wasdk-item-blankwin -> winui3-window wasdk-item-dialog -> winui3-dialog Also update display names and default project names to match. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add winui3-page and winui3-usercontrol item templates Add two new item templates that link existing VS template sources from ItemTemplates/Neutral/CSharp/: winui3-page - BlankPage (Page with XAML and code-behind) winui3-usercontrol - UserControl (UserControl with XAML and code-behind) Both follow the same pattern as winui3-window and winui3-dialog: the template.config is maintained locally while XAML/code-behind are linked from the shared VS template sources. Note: the dotnet new template engine does not support verifying that an existing project exists before adding an item template. The msbuild:RootNamespace binding will fall back to the default value if no project is found. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add project-capability and sdk-version constraints to item templates Item templates (window, page, usercontrol, dialog) should only appear in 'dotnet new list' when run inside a C# project folder. Add a 'project-capability' constraint with 'CSharp' so the templates are hidden when no C# project is found in the current directory. Also add an sdk-version constraint requiring .NET 8.0 or later. Inspired by https://github.com/egvijayanand/winui-templates which uses the same approach. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add sdk-version constraint to project templates Require .NET 8.0 SDK or later for the three project templates (single-project, class-library, unit-test). The templates target net10.0-windows and will not work on older SDKs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * chore(project): update NoWarn property to include CS2008 warning * feat(templates): update template identities to use WinUI naming convention * feat(templates): add symbols section to various template configurations * feat(templates): update dotnetVersion to support .NET 8, 9, and 10 choices * template renamings * User/muyuanli/naming improvements (#6256) * template renamings * Update naming and schema * Add back agents and instructions --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Muyuan Li (from Dev Box) <muyuanli@microsoft.com> Co-authored-by: Muyuan Li <116717757+MuyuanMS@users.noreply.github.com>

* Enhance copilot instructions and project spec * Fix indentation

* complete nuspec * Update dev/VSIX/DotnetNewTemplates/WinAppSdk.CSharp.DotnetNewTemplates.csproj Co-authored-by: Niels Laute <niels.laute@live.nl> * Update dev/VSIX/DotnetNewTemplates/WinAppSdk.CSharp.DotnetNewTemplates.csproj Co-authored-by: Niels Laute <niels.laute@live.nl> * Update dev/VSIX/DotnetNewTemplates/README.md Co-authored-by: Niels Laute <niels.laute@live.nl> * Resolve comments --------- Co-authored-by: Niels Laute <niels.laute@live.nl>

* Update default dotnet version to be 10.0 * Update vstemplate to be dotnet 10 as well

…ws sdk in tfm (#6295)

* set dotnet version based on installed sdk version, and increase windows sdk in tfm * Add test script and fix existing issues with item templates --------- Co-authored-by: Nikola Metulev <nmetulev@users.noreply.github.com>

* added frame and mainpage to main window * winui template updates * adding mvvm template --------- Co-authored-by: Nikola Metulev <711864+nmetulev@users.noreply.github.com>

* Remove invalid classifications and add missing XAML The classications now match the classifications from the VSIX templates * Ensures IDE shows the correct field information Also makes min version a dropdown, and sets default based on current support lifecycles / recommendations. * Add missing min versions

) * Updated icons * Remove assets folder (it already pulls those from the other template) * Layout tweaks to the navview template * Adding a TabView template * Update the MvvM template with counters * Design tweaks for the TabView template * Update icon.png

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

DinahK-2SO · 2026-04-20T08:06:26Z

/azp run

azure-pipelines · 2026-04-20T08:06:48Z

Azure Pipelines successfully started running 1 pipeline(s).

…VSIX

DinahK-2SO · 2026-04-21T06:47:42Z

/azp run

azure-pipelines · 2026-04-21T06:48:03Z

Azure Pipelines successfully started running 1 pipeline(s).

DinahK-2SO · 2026-04-21T07:52:44Z

Our MvvmApp Template doesn't have an icon yet.

Hi @niels9001, @nmetulev and @dotMorten , how did we create the icon for the template (like these ones for the NavigationApp)?

./dev/Templates/Source/ProjectTemplates/Desktop/CSharp/NavigationApp/WinUI.Desktop.Cs.NavigationApp.png

./dev/Templates/Source/ProjectTemplates/Desktop/CSharp/NavigationApp/WinUI.Desktop.Cs.NavigationApp.ico

@DinahK-2SO For the MVVM one, let's use the same as the Blank app as it's currently (mostly) blank anyway :)?

(longer term, I could imagine that you decide what UI template you want, and in the next screen we could have a checkbox that says "Add MVVM"?)

FYI I didn't create those icons when I added them to the templates - I pulled it from the VSIX.

niels9001 · 2026-04-21T07:58:47Z

This PR adds/updates the WinUI App templates:

Add WinUI templates for dotnet new

Add 2 new templates for Visual Studio:

WinUI Navigation App

WinUI TabView App

Add guidelines and scripts for local build

This is looking amazing 🚀!

Question: do we have influence on the order of the template? If so, I'd suggest the following order:

Blank app
NavigationView app
TabView app
Blank app with MVVM
Blank app with WAP
WinUI Class Library
WinUI Unit Test app

Scottj1s · 2026-04-21T21:36:15Z

+
+        Import the VSIX Directory.Build.props for CPM and shared settings.
+    -->
+    <Import Project="$(MSBuildThisFileDirectory)..\VSIX\Directory.Build.props" />


it would be better to factor shared props into a Templates\Directory.Build.props that both Dotnet and VSIX chain into

dotMorten · 2026-04-21T21:42:14Z

@@ -0,0 +1,30 @@
+Microsoft Visual Studio Solution File, Format Version 12.00


Should this be in slnx format now instead?

Scottj1s · 2026-04-21T21:50:06Z

Can't this project use project references to pick up template details (None elements), like the VSIX project does? This approach seems brittle, with the dotnet project needing to know details of each template.

Scottj1s · 2026-04-21T21:52:20Z

Should we add the new item/project templates to the component/standalone VSIXes? Ideally, we'd keep these in sync.

cc: @lauren-ciha

This is how we do it: We create the nuget-version of the templates, and then we just include that nuget in the VSIX installer rather than maintaining two sets of .NET templates.

That's a great approach

Sample by @sayedihashimi here: https://github.com/sayedihashimi/template-sample/tree/main/vsix-with-template

Scottj1s · 2026-04-21T21:55:02Z

might want to chain into this from \BuildAll.ps1

microsoft-github-policy-service Bot added the needs-triage label Apr 16, 2026

DinahK-2SO marked this pull request as ready for review April 17, 2026 07:32

DinahK-2SO changed the title ~~User/muyuanli/dotnetnewtemplate~~ WinUI dotnet new templates Apr 17, 2026

DinahK-2SO changed the title ~~WinUI dotnet new templates~~ WinUI templates for dotnet new and VSIX Apr 17, 2026

DinahK-2SO requested review from Scottj1s, Copilot and yeelam-gordon and removed request for yeelam-gordon April 17, 2026 19:17

Copilot AI reviewed Apr 17, 2026

View reviewed changes

DinahK-2SO force-pushed the user/muyuanli/dotnetnewtemplate branch from 75d7c86 to e3fc78f Compare April 20, 2026 03:33

MuyuanMS and others added 20 commits April 20, 2026 16:02

Create Dotnet New Template Branch

a3b1d80

Unblocking single proj and item template from building

f0659d9

Add template csproj package reference specific to dotnet new template

290d0db

Remove multi-project packaged template

7f5bd2c

feat(docs): add design principles, globalization, performance, securi…

e2b591a

…ty, and testing guidelines (#6217)

User/muyuanli/add template pipeline (#6218)

3a1f888

* Add pipelines * Update readme

docs(instructions): enhance guidelines for API usage and sample searc…

653b3e2

…hing

User/muyuanli/improve template (#6259)

acf07ec

* Enhance copilot instructions and project spec * Fix indentation

Agent MD minor fixes (#6262)

182ac8c

Update default dotnet version to be 10.0 (#6282)

a3d455e

* Update default dotnet version to be 10.0 * Update vstemplate to be dotnet 10 as well

set dotnet version based on installed sdk version, and increase windo…

74c77a3

…ws sdk in tfm (#6295)

Add test script and fix issue with item templates (#6303)

d410c62

* set dotnet version based on installed sdk version, and increase windows sdk in tfm * Add test script and fix existing issues with item templates --------- Co-authored-by: Nikola Metulev <nmetulev@users.noreply.github.com>

Merge Build and Publish Pipeline (#6320)

2f9c0b0

WinUI3 dotnet new tempalte updates (#6359)

6a5a719

* added frame and mainpage to main window * winui template updates * adding mvvm template --------- Co-authored-by: Nikola Metulev <711864+nmetulev@users.noreply.github.com>

merge ado

d4466e3

niels9001 and others added 10 commits April 20, 2026 16:02

Set DefaultContentDialogStyle on ContentDialog item template

6d3c0a0

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

guideline for local build vsix package

4861786

installation script for local built vsix

bd83631

reveal the TabViewApp and NavigationApp templates

152f3b4

check dependent components

ba8011b

refactoring the templates path 1

88b716d

refactoring the templates path 2; add test pipelines

c1e21d0

the test pipeline stage

0140a0b

fix pipeline error

ed2687a

fix error; enable pipeline failOnStderr

f619e83

DinahK-2SO force-pushed the user/muyuanli/dotnetnewtemplate branch from 4258460 to f619e83 Compare April 20, 2026 08:02

inherit from VSIX/Directory.Build.props - fix pfx cert error in build…

7e51419

…VSIX

DinahK-2SO commented Apr 21, 2026

View reviewed changes

Scottj1s reviewed Apr 21, 2026

View reviewed changes

dotMorten reviewed Apr 21, 2026

View reviewed changes

Scottj1s reviewed Apr 21, 2026

View reviewed changes

		@@ -0,0 +1,30 @@
		Microsoft Visual Studio Solution File, Format Version 12.00

Conversation

DinahK-2SO commented Apr 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

DinahK-2SO commented Apr 20, 2026

Uh oh!

azure-pipelines Bot commented Apr 20, 2026

Uh oh!

DinahK-2SO commented Apr 21, 2026

Uh oh!

azure-pipelines Bot commented Apr 21, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

niels9001 commented Apr 21, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

8 participants

DinahK-2SO commented Apr 16, 2026 •

edited

Loading