aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging,…
@managedcodeInstall SkillDevelopment
Skill
/legacy-aspnet
Maintain classic ASP.NET applications on .NET Framework, including Web Forms, older MVC, and legacy hosting patterns, while planning realistic modernization boundaries. USE FOR: working in Web Forms, legacy MVC, or classic ASP.NET applications; reviewing old IIS-centric
Claude Code
$ npx -y skills add managedcode/dotnet-skills --skill legacy-aspnet --agent claude-code
Codex
$ npx skills add managedcode/dotnet-skills --skill legacy-aspnet -a codex -y
Cursor
$ npx skills add managedcode/dotnet-skills --skill legacy-aspnet -a cursor -y
Gemini CLI
$ npx skills add managedcode/dotnet-skills --skill legacy-aspnet -a gemini-cli -y
GitHub Copilot
$ npx skills add managedcode/dotnet-skills --skill legacy-aspnet -a github-copilot -y
OpenCode
$ npx skills add managedcode/dotnet-skills --skill legacy-aspnet -a opencode -y
Windsurf
$ npx skills add managedcode/dotnet-skills --skill legacy-aspnet -a windsurf -y
SKILL.md
legacy-aspnet.SKILL.mdname: legacy-aspnet
description: "Maintain classic ASP.NET applications on .NET Framework, including Web Forms, older MVC, and legacy hosting patterns, while planning realistic modernization boundaries. USE FOR: working in Web Forms, legacy MVC, or classic ASP.NET applications; reviewing old IIS-centric configuration and lifecycle behavior; planning migration toward ASP.NET Core. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made."
compatibility: "Requires classic ASP.NET on .NET Framework."
Legacy ASP.NET
Trigger On
- working in Web Forms, legacy MVC, or classic ASP.NET applications
- reviewing old IIS-centric configuration and lifecycle behavior
- planning migration toward ASP.NET Core without breaking core business flows
Workflow
1. Treat classic ASP.NET as a distinct stack with different hosting, lifecycle, and configuration rules from ASP.NET Core. 2. Stabilize behavior first: routing, session, auth, server controls, configuration transforms, and deployment assumptions. 3. Plan modernization in seams: isolate domain and service logic, then move replaceable edges instead of rewriting the whole app at once. 4. Use `wcf` or `entity-framework6` when the legacy app depends on those subsystems rather than flattening them into generic web work. 5. Be careful with guidance copied from ASP.NET Core because middleware, DI, and hosting assumptions do not transfer directly. 6. Validate in an environment that resembles real IIS and configuration transforms.
Deliver
- practical maintenance guidance for classic ASP.NET
- stabilized legacy behavior and modernization seams
- a migration path that avoids unnecessary risk
Validate
- classic and Core guidance are not mixed
- legacy runtime assumptions are preserved deliberately
- migration steps are incremental and testable
References
- [Migration Paths](references/migration.md): strategies for migrating from ASP.NET to ASP.NET Core, including incremental migration, strangler fig pattern, and component-specific guidance
- [Maintenance Patterns](references/patterns.md): stabilization and maintenance patterns for legacy ASP.NET code, including abstraction layers, testing seams, and deployment practices
Read more
name: legacy-aspnet description: "Maintain classic ASP.NET applications on .NET Framework, including Web Forms, older MVC, and legacy hosting patterns, while planning realistic modernization boundaries. USE FOR: working in Web Forms, legacy MVC, or classic ASP.NET applications; reviewing old IIS-centric configuration and lifecycle behavior; planning migration toward ASP.NET Core. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made." compatibility: "Requires classic ASP.NET on .NET Framework."
Legacy ASP.NET
Trigger On
- working in Web Forms, legacy MVC, or classic ASP.NET applications
- reviewing old IIS-centric configuration and lifecycle behavior
- planning migration toward ASP.NET Core without breaking core business flows
Workflow
1. Treat classic ASP.NET as a distinct stack with different hosting, lifecycle, and configuration rules from ASP.NET Core. 2. Stabilize behavior first: routing, session, auth, server controls, configuration transforms, and deployment assumptions. 3. Plan modernization in seams: isolate domain and service logic, then move replaceable edges instead of rewriting the whole app at once. 4. Use `wcf` or `entity-framework6` when the legacy app depends on those subsystems rather than flattening them into generic web work. 5. Be careful with guidance copied from ASP.NET Core because middleware, DI, and hosting assumptions do not transfer directly. 6. Validate in an environment that resembles real IIS and configuration transforms.
Deliver
- practical maintenance guidance for classic ASP.NET
- stabilized legacy behavior and modernization seams
- a migration path that avoids unnecessary risk
Validate
- classic and Core guidance are not mixed
- legacy runtime assumptions are preserved deliberately
- migration steps are incremental and testable
References
- [Migration Paths](references/migration.md): strategies for migrating from ASP.NET to ASP.NET Core, including incremental migration, strangler fig pattern, and component-specific guidance
- [Maintenance Patterns](references/patterns.md): stabilization and maintenance patterns for legacy ASP.NET code, including abstraction layers, testing seams, and deployment practices
Stats
515
Stars
41
Forks
Active
Maintenance
C#
Language
MIT
License
Last commit
Created
Ships withdotnet-skills
Stop explaining .NET to your AI. Start building. We've all been there: asking Claude to use Entity Framework, only to get EF6 patterns in a .NET 8 project. Explaining to Copilot that Blazor Server and Blazor WebAssembly aren't the same thing.
499200 skills17 agents
Stars on GitHub
Momentum
- stars in total
- 499
Other skills on dotnet-skills.
@managedcodeInstall Skillaspire
Build, upgrade, and operate Aspire 13.5.x C# or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults,…
@managedcodeInstall Skillavalonia
Build and debug Avalonia 11/12 .NET applications with XAML, compiled bindings, MVVM, custom controls, desktop lifetimes, and…
@managedcodeInstall Skillazure-functions
Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable…
@managedcodeInstall Skillblazor
Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design,…
@managedcodeInstall Skillentity-framework6
Maintain or migrate EF6-based applications with realistic guidance on what to keep, what to modernize, and when EF Core is or is…
@managedcodeInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about legacy-aspnet.
- Which coding agents can use legacy-aspnet?
- legacy-aspnet installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.