메뉴
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.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill webforms-to-blazor-upgrade명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
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.
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.
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.
SKILL.md 표시 중
SOC 직업 분류 기준
| 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"]} |
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.
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.
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.
Do you want to proceed with {user's choice} anyway, or switch to the recommended Blazor Server target?
Follow the dotnet-version-upgrade scenario skill for all stages (assessment, planning, execution).
