chore(samples): update sample package versions (patch and minor)

Ouverte
  • Quelque chose ne va pas ?
#588 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
45/100
Type d'issue
Refactorisation
Clarté
Clairement spécifiée
Activité
Active
Stack technique
csharp, github-actions
Domaine
build-system, devops

Piste de recherche

Start by reviewing the listed sample project files, Directory.Packages.props, Directory.Build.props, and global.json to confirm each package's current version and scope. Verify the target versions on NuGet, then update only the specified references and run the sample builds available locally; do not install mobile workloads. Done means CI's build-samples.yml jobs pass and the specified package versions match the targets.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

dependencies Examples

Part 2 of the outdated-package sweep (dotnet-outdated 4.8.1, 2026-11-05). Brings the samples up to date for patch and minor versions. Related: #584 / PR #586 already bumped Microsoft.AspNetCore.Components.WebAssembly.Server to 10.0.14 in the Blazor WASM server.

Scope (this PR only)

Only files under samples/. Samples reference published NuGet packages, not the in-repo projects.

Datasync packages: 10.1.0 -> 10.1.2

CommunityToolkit.Datasync.Client, .Server, .Server.EntityFrameworkCore, .Server.InMemory in:

  • samples/todoapp-tutorial/ClientApp/ClientApp.csproj, samples/todoapp-tutorial/ServerApp/ServerApp.csproj
  • samples/todoapp-blazor-wasm/TodoApp.BlazorWasm.Client|Server/*.csproj
  • samples/todoapp-mvc/TodoApp.Service/TodoApp.Service.csproj
  • samples/todoapp/TodoApp.Avalonia/TodoApp.Avalonia/*.csproj, TodoApp.MAUI, TodoApp.WPF, TodoApp.WinUI3
  • samples/todoapp/TodoApp.Uno/Directory.Packages.props
Microsoft 10.0.9 -> 10.0.14

Microsoft.EntityFrameworkCore, .InMemory, .SqlServer, .Tools, Microsoft.AspNetCore.OpenApi, Microsoft.AspNetCore.Components.WebAssembly and .DevServer (keep PrivateAssets="all"), Microsoft.Extensions.Http, Microsoft.Extensions.DependencyInjection (WinUI3), Microsoft.Extensions.Logging.Debug (MAUI), System.IO.Packaging (Uno props).
Affected: datasync-server/src/Sample.Datasync.Server, todoapp-blazor-wasm/*, todoapp-mvc/TodoApp.Service, todoapp/TodoApp.Avalonia/TodoApp.Avalonia, TodoApp.MAUI, TodoApp.WinUI3, TodoApp.Uno.

Other patches
Package Current -> Target Where
CommunityToolkit.Mvvm 8.4.0 -> 8.4.2 tutorial ClientApp, Avalonia, MAUI, WPF, WinUI3
SQLitePCLRaw.bundle_e_sqlite3 3.0.3 -> 3.0.5 all client samples + Uno props (keep the NU1903 comment in Uno props; must stay 3.x)
Avalonia, Avalonia.Desktop, Avalonia.Fonts.Inter, Avalonia.Themes.Fluent, Avalonia.Android, Avalonia.iOS 12.1.0 -> 12.1.5 change <AvaloniaVersion> in samples/todoapp/TodoApp.Avalonia/Directory.Build.props only
CommunityToolkit.WinUI.Behaviors, .Converters 8.2.250402 -> 8.2.251219 TodoApp.WinUI3.csproj, Uno props
Microsoft.Windows.SDK.BuildTools 10.0.26100.3916 -> 10.0.28000.2957 TodoApp.WinUI3.csproj (do not change Microsoft.WindowsAppSDK; that is a separate issue)
Microsoft.Web.LibraryManager.Build 3.0.71 -> 3.0.114 todoapp-mvc/TodoApp.Service
Minor bumps (could not be scanned locally: need mobile workloads; verify via CI only)
Package Current -> Target Where
Microsoft.Maui.Controls 10.0.40 -> 10.0.120 TodoApp.MAUI.csproj
Xamarin.AndroidX.Core.SplashScreen 1.0.1.15 -> 1.2.0.3 TodoApp.Avalonia.Android.csproj
Uno SDK 6.5.36 -> 6.7.45 samples/todoapp/TodoApp.Uno/global.json (msbuild-sdks.Uno.Sdk), not the props file

If a CI job for MAUI, Uno or Avalonia.Android fails after one of these three bumps and the fix is not trivial, revert that single bump, note it in the PR description, and open a follow-up issue rather than blocking the rest.

Explicitly NOT in this PR
  • Microsoft.WindowsAppSDK 1.7 -> 2.x (separate issue).
  • Microsoft.OData.Core/Edm 8.4.3 in datasync-server and datasync-server-cosmosdb-singlecontainer: bump to 8.4.4 only (patch, same line), not 9.0.0 (separate blocked issue).
  • Refit 8.0.0 in TodoApp.Uno/Directory.Packages.props: there is no PackageReference to it in the csproj (it is an Uno SDK implicit package version). The reported "latest 16.4.0" is a different version scheme; leave unchanged and mention in the PR.

Steps

  1. Verify target versions exist on NuGet (https://api.nuget.org/v3-flatcontainer/<lowercase-id>/index.json).
  2. Make the edits. Samples cannot all be built locally (per AGENTS.md: do not install workloads). Locally build only what works, e.g. cd samples/todoapp-blazor-wasm && dotnet build TodoApp.BlazorWasm.sln, samples/todoapp-tutorial, samples/todoapp-mvc/part5.sln, samples/datasync-server.
  3. Push the branch to the fork and dispatch build-samples.yml with --ref <branch>; watch all jobs plus all-samples-built (~6-8 min).
  4. Re-run dotnet-outdated on each sample solution (use EnableWindowsTargeting=true for WPF/WinUI3) and confirm only the explicitly excluded packages remain.

Acceptance criteria

  • Packages above at target versions; build-samples.yml all green.
  • No vulnerability warnings (NU190x) in sample restores.
  • PR title: chore(samples): update sample package versions.
Langage dominant
C#
Étoiles
184
Forks
48
Merge moyen
21 min
PR mergées (30 j)
7

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de CommunityToolkit/Datasync

Toutes les issues de CommunityToolkit/Datasync

Issues similaires

Plus d'issues C#

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.