webforms-to-blazor-upgrade

Upgrade ASP.NET Web Forms projects to modern .NET. Use when the user wants to upgrade, migrate, modernize, port, convert, or move Web Forms / WebForms / .aspx pages to any modern .NET. framework.

Jump to install

Repository: microsoft/upgrade-agent-plugins
Last source activity: June 19, 2026 at 15:01
Detected SKILL.md language: English
Stars: 29
Forks: 4

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill webforms-to-blazor-upgrade

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

migrating-csharp-nullable-references

Enable nullable reference types in a C# project and systematically resolve all warnings. Use when adopting NRTs in existing codebases, performing file-by-file or project-wide nullable migration, fixing CS8602/CS8618/CS86xx warnings, annotating APIs for nullability, cleaning up null-forgiving operators, or upgrading dependencies with new nullable annotations. Also use when the user asks to "enable nullable", "turn on NRTs", "annotate for nullability", "fix nullable warnings", or "migrate to nullable reference types". DO NOT USE FOR: projects already fully migrated with zero warnings (unless auditing suppressions), fixing a handful of nullable warnings in code that already has NRTs enabled, suppressing warnings without fixing them, C# 7.3 or earlier projects. INVOKES: Get-NullableReadiness.ps1 scanner script.

2026-08-20

managing-shared-database-schema

Governs a SQL database that two hosts read and write at the same time during a side-by-side migration. Use when a legacy .NET Framework app and a new .NET app share one database, point at the same connection string, or must both stay live while the schema changes. Covers which toolchain owns schema changes, expand-then-contract (additive-only) evolution, dual-write and backfill ordering, deployment ordering, and rollback rules. Triggers for "shared database", "who runs migrations", "dual write", "zero downtime schema change", or "add a column safely". Applies to EF6, EF Core, Dapper, ADO.NET, DACPAC/SqlPackage, DbUp and Flyway, and explains how EF6's __MigrationHistory and EF Core's __EFMigrationsHistory coexist without merging. Also use before deleting a Migrations folder, before enabling Database.Migrate() at startup, or when asked whether renaming or dropping a column is safe while the old app is live.

2026-08-20

migrating-edmx-to-code-first

Migrates Entity Framework 6 EDMX-based models (Database-First/Model-First) to EF Core Code-First. Use when upgrading projects containing .edmx files, .Context.tt templates, EntityClient connection strings, or ObjectContext references. Triggers for "migrate EDMX", "convert EDMX to code first", "EF6 to EF Core", "remove EDMX", "database first to code first", and "scaffold DbContext". Also relevant when encountering EntitySQL, EntityObject, or ObjectSet patterns during .NET modernization.

2026-08-20

View all from this repository

Web Forms to Blazor Upgrade Scenario

This scenario uses the dotnet-version-upgrade scenario workflow. The only differences are intent detection and target technology selection — this skill matches Web Forms upgrade requests specifically and always targets Blazor (Blazor Server) as the modernization destination.

Target Technology — Default Lock with Opt-Out

When Web Forms (.aspx, .ascx, .master, .asmx, System.Web.UI, <%@ Page %> directives, server controls, Global.asax, WebForm project type GUID {349C5851-65DF-11DA-9384-00065B846F21}) is detected, the default and strongly recommended upgrade target is Blazor Server. Blazor Server is the only target with full, validated support in this scenario.

When the user explicitly insists on a non-Blazor target

If — and only if — the user explicitly asks to target Razor Pages, ASP.NET Core MVC, Minimal APIs, Web API, or another non-Blazor framework, honor their choice rather than refusing. Before proceeding, deliver a clear warning once and get acknowledgment:

⚠️ Unsupported target warning This scenario is designed and validated for migrating Web Forms projects to Blazor Server. You've asked to target {user's choice} instead.

There is no first-class support in this scenario for {user's choice}.
Expect reduced guidance, more manual decisions, and a higher chance of incomplete or incorrect transformations.
Assessment and high-level planning will still work, but execution will rely on general .NET knowledge rather than scenario-specific patterns.

Do you want to proceed with {user's choice} anyway, or switch to the recommended Blazor Server target?

Workflow

Follow the dotnet-version-upgrade scenario skill for all stages (assessment, planning, execution).

Web Forms to Blazor Upgrade Scenario

Target Technology — Default Lock with Opt-Out

When the user explicitly insists on a non-Blazor target

⚠️ Unsupported target warning This scenario is designed and validated for migrating Web Forms projects to Blazor Server. You've asked to target {user's choice} instead.

There is no first-class support in this scenario for {user's choice}.
Expect reduced guidance, more manual decisions, and a higher chance of incomplete or incorrect transformations.
Assessment and high-level planning will still work, but execution will rely on general .NET knowledge rather than scenario-specific patterns.

Do you want to proceed with {user's choice} anyway, or switch to the recommended Blazor Server target?

Workflow

Follow the dotnet-version-upgrade scenario skill for all stages (assessment, planning, execution).

name	webforms-to-blazor-upgrade
description	Upgrade ASP.NET Web Forms projects to modern .NET. Use when the user wants to upgrade, migrate, modernize, port, convert, or move Web Forms / WebForms / .aspx pages to any modern .NET. framework.
metadata	{"discovery":"scenario","importance":"high","traits":"(.NET\|CSharp\|VisualBasic) & DotNetFramework & WebForms","scenarioTraitsSet":[".NET","DotNetFramework","WebForms"]}

name	webforms-to-blazor-upgrade
description	Upgrade ASP.NET Web Forms projects to modern .NET. Use when the user wants to upgrade, migrate, modernize, port, convert, or move Web Forms / WebForms / .aspx pages to any modern .NET. framework.
metadata	{"discovery":"scenario","importance":"high","traits":"(.NET\|CSharp\|VisualBasic) & DotNetFramework & WebForms","scenarioTraitsSet":[".NET","DotNetFramework","WebForms"]}

webforms-to-blazor-upgrade

Source facts

Install options

Review the source files

More from this repository