Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fritzandfriends/bwfc-migration
Migrate ASP.NET Web Forms applications to Blazor Server using the webforms-to-blazor CLI tool and BlazorWebFormsComponents (BWFC). Orchestrates L1 automated transforms via CLI, then guides L2 contextual transforms. WHEN: "migrate aspx", "convert web forms", "web forms to blazor", "run migration". INVOKES: webforms-to-blazor CLI tool. FOR SINGLE OPERATIONS: use /bwfc-identity-migration for auth, /bwfc-data-migration for EF/architecture.
Passed 21 of 22 test cases with the skill, and 8 of 22 without it.
and 17 more in the full report
13 fixed8 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
In a converted Blazor Server component, legacy code-behind reads form values using Request.Form["txtName"]. What BWFC component wrapper enables Request.Form access in interactive Blazor mode?
| Checked | Without skill | With skill |
|---|---|---|
| Wraps input components in WebFormsForm component | Missed | Passed |
The instructions your model reads when the skill loads.
This skill orchestrates the full migration from ASP.NET Web Forms to Blazor Server using a three-layer architecture:
| Layer | Executor | Coverage | Description |
|---|---|---|---|
| L1: Deterministic | webforms-to-blazor CLI tool | ~70% | 27 compiled transforms (16 markup + 11 code-behind), project scaffolding, config migration |
| L2: Contextual | Copilot (this skill) | ~15–20% | TODO-driven transforms requiring semantic understanding — session state, lifecycle, data binding |
| L3: Architectural | Developer | ~10–15% | Business logic, custom controls, auth flows, architectural decisions |
The CLI tool emits structured // TODO(bwfc-*) comments and a JSON migration report. L2 reads that report and applies contextual transforms per TODO category.
Three-layer migration architecture:
dotnet tool install -g Fritz.WebFormsToBlazor
ALWAYS inherit from WebFormsPageBase (via _Imports.razor) and use the Web Forms shims. The BlazorWebFormsComponents library provides shims that make Web Forms patterns work AS-IS in Blazor — no manual rewrites needed.
<asp:ListView>, <asp:FormView>, <asp:GridView>, <asp:DataList>, or <asp:Repeater> with manual HTML, hand-built <table> markup, or @foreach loops.<ListView>, <FormView>, <GridView>, <DataList>, <Repeater>.test cases passed, vs 8 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.