chore(samples): update WinUI3 sample to Windows App SDK 2.x

Open
  • Is something wrong?
#593 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
40/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
build-system

Research direction

Start with samples/todoapp/TodoApp.WinUI3/TodoApp.WinUI3.csproj and the Windows App SDK 2.x release notes and migration guide; first resolve the related sample package version issue. Check toolkit compatibility and the WinUI3 instructions in docs/samples/todoapp/winui3.md, then restore locally and validate the build on the Windows CI runner. Done means CI builds the sample on 2.x, or the issue records why the upgrade is deferred.

Written by the indexing model from the issue text.

Description

dependencies Examples

Part 7 of the outdated-package sweep (dotnet-outdated 4.8.1, 2026-11-05). Major upgrade of the WinUI3 sample's Windows App SDK. This can only be validated on the Windows CI runner (and cannot be built on macOS: EnableWindowsTargeting=true allows restore only).

Current state

samples/todoapp/TodoApp.WinUI3/TodoApp.WinUI3.csproj:

Things to investigate

  • Windows App SDK 2.x release notes and migration guide: https://learn.microsoft.com/windows/apps/windows-app-sdk/ (look at "Windows App SDK 2.0" notes), including minimum Windows version, TFM (net10.0-windows10.0.xxxxx), required Microsoft.Windows.SDK.BuildTools version, packaging/unpackaged-deployment changes, and Microsoft.WindowsAppSDK being split into component packages.
  • Compatibility of CommunityToolkit.WinUI.Behaviors / .Converters 8.2.x with WinAppSDK 2.x. If incompatible, document and either find a compatible version or defer.
  • TodoApp.Uno also uses these toolkit packages via the Uno SDK; changing WinUI3 must not change Uno.
  • Docs for the sample: docs/samples/todoapp/winui3.md; update any version-specific instructions.

Steps

  1. Bump the package; adjust the csproj (TFM, WindowsSdkPackageVersion, etc.) and any XAML/C# per the migration guide.
  2. Locally: only dotnet restore with EnableWindowsTargeting=true (don't try to build; AGENTS.md says not to install workloads).
  3. Push the branch to the fork and dispatch build-samples.yml (or build-samples-todoapp-windows.yml) with --ref <branch>; the Windows job must be green.
  4. If the upgrade proves too large, stop, document findings in this issue, and leave the sample on 1.x (adding a note about the support lifecycle).

Acceptance criteria

  • WinUI3 sample builds in CI on WinAppSDK 2.x, or this issue documents why it is deferred.
  • PR title: chore(samples): update WinUI3 sample to Windows App SDK 2.x.
Dominant language
C#
Stars
184
Forks
48
Avg merge
21m
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CommunityToolkit/Datasync

All issues in CommunityToolkit/Datasync

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.