migrate-dotnet9-to-dotnet10

Migrate a .NET 9 project or solution to .NET 10 and resolve all breaking changes. USE FOR: upgrading TargetFramework from net9.0 to net10.0, fixing build errors after updating the .NET 10 SDK, resolving source and behavioral changes in .NET 10 / C# 14 / ASP.NET Core 10 / EF Core 10, updating Dockerfiles for Debian-to-Ubuntu base images, resolving obsoletion warnings (SYSLIB0058-SYSLIB0062), adapting to SDK/NuGet changes (NU1510, PrunePackageReference), migrating System.Linq.Async to built-in AsyncEnumerable, fixing OpenApi v2 API changes, cryptography renames, and C# 14 compiler changes (field keyword, extension keyword, span overloads). DO NOT USE FOR: .NET Framework migrations, upgrading from .NET 8 or earlier (use migrate-dotnet8-to-dotnet9 first), greenfield .NET 10 projects, or cosmetic modernization. LOADS REFERENCES: csharp-compiler, core-libraries, sdk-msbuild (always); aspnet-core, efcore, cryptography, extensions-hosting, serialization-networking, winforms-wpf, containers-interop (selective).

Aller à l'installation

Dépôt: runceel/ReactiveProperty
Dernière activité de la source: 20 juin 2026 à 11:21
Langue détectée de SKILL.md: anglais
Étoiles: 940
Forks: 104

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/runceel/ReactiveProperty --skill migrate-dotnet9-to-dotnet10

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers

11 fichiers

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

development-workflow

ReactiveProperty repository development policy. Use whenever you implement a feature or bug fix, change library or test code under Source/ or Test/, make a design or architecture decision, or write documentation in this repo. Enforces strict Test-Driven Development (Red -> Green -> Refactor) with MSTest and `dotnet test ReactiveProperty.slnx`, requires recording design decisions as ADRs under dev-docs/adr/, and defines the documentation split: docs/ is user-facing (plain Markdown browsed on GitHub) while dev-docs/ holds implementer/contributor documentation. Triggers include "implement", "add feature", "fix bug", "TDD", "red green refactor", "design decision", "architecture", "ADR", "where do docs go", and "contributor docs".

2026-07-05

migrating-reactiveproperty-to-r3

Migrate an application from ReactiveProperty (namespace Reactive.Bindings) to R3 plus the ReactiveProperty.R3 bridge package. Use this when asked to "migrate to R3", "move off ReactiveProperty", "replace ReactiveProperty with R3", "swap Reactive.Bindings for R3", or to rewrite ViewModels/commands/validation/notifiers/collections that use ReactiveProperty so they run on R3. Drives the rewrite from a mapping table (references/rules.json): everything R3 already provides becomes native R3, every genuine gap becomes a ReactiveProperty.R3 type, and the few cases that cannot be rewritten mechanically are flagged for manual review.

2026-06-28

releasing-reactiveproperty

Release the ReactiveProperty NuGet package set from this repository. Use this skill whenever the user asks to release, publish, ship, pre-release/prerelease, stable release, tag v*, push NuGet packages, or mentions "リリース", "pre リリース", "正式リリース", "NuGet 公開", or "パッケージ公開" for ReactiveProperty, even if they do not use the skill name. Handles tag-driven releases, mode/version confirmation, GitHub Actions monitoring, NuGet/GitHub Release verification, and failure guardrails. Do not use for setting up NuGet OIDC/trusted publishing; use nuget-trusted-publishing instead.

2026-06-24

Tout voir dans ce dépôt

.NET 9 → .NET 10 Migration

Migrate a .NET 9 project or solution to .NET 10, systematically resolving all breaking changes. The outcome is a project targeting net10.0 that builds cleanly, passes tests, and accounts for every behavioral, source-incompatible, and binary-incompatible change introduced in the .NET 10 release.

When to Use

Upgrading TargetFramework from net9.0 to net10.0

Resolving build errors or new warnings after updating the .NET 10 SDK

Adapting to behavioral changes in .NET 10 runtime, ASP.NET Core 10, or EF Core 10

.NET 9 → .NET 10 Migration

When to Use

Upgrading TargetFramework from net9.0 to net10.0

Resolving build errors or new warnings after updating the .NET 10 SDK

Adapting to behavioral changes in .NET 10 runtime, ASP.NET Core 10, or EF Core 10

Input	Required	Description
Project or solution path	Yes	The `.csproj`, `.sln`, or `.slnx` entry point to migrate
Build command	No	How to build (e.g., `dotnet build`, a repo build script). Auto-detect if not provided
Test command	No	How to run tests (e.g., `dotnet test`). Auto-detect if not provided
Project type hints	No	Whether the project uses ASP.NET Core, EF Core, WinForms, WPF, containers, etc. Auto-detect from PackageReferences and SDK attributes if not provided

If the project uses…	Load reference
Any .NET 10 project	`references/csharp-compiler-dotnet9to10.md`
Any .NET 10 project	`references/core-libraries-dotnet9to10.md`
Any .NET 10 project	`references/sdk-msbuild-dotnet9to10.md`
ASP.NET Core	`references/aspnet-core-dotnet9to10.md`
Entity Framework Core	`references/efcore-dotnet9to10.md`
Cryptography APIs	`references/cryptography-dotnet9to10.md`
Microsoft.Extensions.Hosting, BackgroundService, configuration	`references/extensions-hosting-dotnet9to10.md`
System.Text.Json, XmlSerializer, HttpClient, MailAddress, Uri	`references/serialization-networking-dotnet9to10.md`
Windows Forms or WPF	`references/winforms-wpf-dotnet9to10.md`
Docker containers, single-file apps, native interop	`references/containers-interop-dotnet9to10.md`

Reference file	When to load
`references/csharp-compiler-dotnet9to10.md`	Always (C# 14 compiler breaking changes — field keyword, extension keyword, span overloads)
`references/core-libraries-dotnet9to10.md`	Always (applies to all .NET 10 projects)
`references/sdk-msbuild-dotnet9to10.md`	Always (SDK and build tooling changes)
`references/aspnet-core-dotnet9to10.md`	Project uses ASP.NET Core
`references/efcore-dotnet9to10.md`	Project uses Entity Framework Core or Microsoft.Data.Sqlite
`references/cryptography-dotnet9to10.md`	Project uses System.Security.Cryptography or X.509 certificates
`references/extensions-hosting-dotnet9to10.md`	Project uses Generic Host, BackgroundService, or Microsoft.Extensions.Configuration
`references/serialization-networking-dotnet9to10.md`	Project uses System.Text.Json, XmlSerializer, HttpClient, or networking APIs
`references/winforms-wpf-dotnet9to10.md`	Project uses Windows Forms or WPF
`references/containers-interop-dotnet9to10.md`	Project uses Docker containers, single-file publishing, or native interop (P/Invoke)

migrate-dotnet9-to-dotnet10

Options d'installation

Vérifiez les fichiers source

.NET 9 → .NET 10 Migration

When to Use

.NET 9 → .NET 10 Migration

When to Use

When Not to Use

Inputs

Workflow

Step 1: Assess the project

Step 2: Update the Target Framework

Step 3: Resolve build errors and source-incompatible changes

Step 4: Address behavioral changes

Step 5: Update infrastructure

Step 6: Verify

Reference Documents

description	Migrate a .NET 9 project or solution to .NET 10 and resolve all breaking changes. USE FOR: upgrading TargetFramework from net9.0 to net10.0, fixing build errors after updating the .NET 10 SDK, resolving source and behavioral changes in .NET 10 / C# 14 / ASP.NET Core 10 / EF Core 10, updating Dockerfiles for Debian-to-Ubuntu base images, resolving obsoletion warnings (SYSLIB0058-SYSLIB0062), adapting to SDK/NuGet changes (NU1510, PrunePackageReference), migrating System.Linq.Async to built-in AsyncEnumerable, fixing OpenApi v2 API changes, cryptography renames, and C# 14 compiler changes (field keyword, extension keyword, span overloads). DO NOT USE FOR: .NET Framework migrations, upgrading from .NET 8 or earlier (use migrate-dotnet8-to-dotnet9 first), greenfield .NET 10 projects, or cosmetic modernization. LOADS REFERENCES: csharp-compiler, core-libraries, sdk-msbuild (always); aspnet-core, efcore, cryptography, extensions-hosting, serialization-networking, winforms-wpf, containers-interop (selective).
metadata	{"github-path":"plugins/dotnet-upgrade/skills/migrate-dotnet9-to-dotnet10","github-pinned":"v1.0.0","github-ref":"refs/tags/v1.0.0","github-repo":"https://github.com/dotnet/skills","github-tree-sha":"566845910e3c74dc0a6156e48a99b67b762d3259"}
name	migrate-dotnet9-to-dotnet10

migrate-dotnet9-to-dotnet10

Informations de source

Options d'installation

Vérifiez les fichiers source

Plus depuis ce dépôt

.NET 9 → .NET 10 Migration

When to Use

Plus depuis ce dépôt

.NET 9 → .NET 10 Migration

When to Use

When Not to Use

Inputs

Workflow

Step 1: Assess the project

Step 2: Update the Target Framework

Step 3: Resolve build errors and source-incompatible changes

Step 4: Address behavioral changes

Step 5: Update infrastructure

Step 6: Verify

Reference Documents