How do I install the Legacy Aspnet skill?

Run npx skillmds@latest add managedcode/legacy-aspnet in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Legacy Aspnet safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Legacy Aspnet?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Legacy Aspnet free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Legacy Aspnet?

managedcode (@managedcode) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Legacy Aspnet by managedcode — Agent Skill

Name: Legacy Aspnet
Author: managedcode

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 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.

managedcode 3890f86 4 files · 21.4 KB Updated Sep 17, 2026

File contents

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

Treat classic ASP.NET as a distinct stack with different hosting, lifecycle, and configuration rules from ASP.NET Core.
Stabilize behavior first: routing, session, auth, server controls, configuration transforms, and deployment assumptions.
Plan modernization in seams: isolate domain and service logic, then move replaceable edges instead of rewriting the whole app at once.
Use wcf or entity-framework6 when the legacy app depends on those subsystems rather than flattening them into generic web work.
Be careful with guidance copied from ASP.NET Core because middleware, DI, and hosting assumptions do not transfer directly.
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: strategies for migrating from ASP.NET to ASP.NET Core, including incremental migration, strangler fig pattern, and component-specific guidance
Maintenance Patterns: stabilization and maintenance patterns for legacy ASP.NET code, including abstraction layers, testing seams, and deployment practices

---name: legacy-aspnetdescription: 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.---# 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## Workflow1. 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

Frequently asked questions