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

Abierto
  • ¿Algo no está bien?
#593 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
40/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp
Área
build-system

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
C#
Estrellas
184
Forks
48
Merge medio
21 min
PR fusionados (30 d)
7

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CommunityToolkit/Datasync

Todos los issues de CommunityToolkit/Datasync

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.