legacy-aspnet
starsforks
How to install legacy-aspnet?
managedcode/dotnet-skills/legacy-aspnet
$npx -y skills add managedcode/dotnet-skills --skill legacy-aspnetMaintain 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 configura
SKILL.md
| 1 | # Legacy ASP.NET |
| 2 | |
| 3 | ## Trigger On |
| 4 | |
| 5 | - working in Web Forms, legacy MVC, or classic ASP.NET applications |
| 6 | - reviewing old IIS-centric configuration and lifecycle behavior |
| 7 | - planning migration toward ASP.NET Core without breaking core business flows |
| 8 | |
| 9 | ## Workflow |
| 10 | |
| 11 | 1. Treat classic ASP.NET as a distinct stack with different hosting, lifecycle, and configuration rules from ASP.NET Core. |
| 12 | 2. Stabilize behavior first: routing, session, auth, server controls, configuration transforms, and deployment assumptions. |
| 13 | 3. Plan modernization in seams: isolate domain and service logic, then move replaceable edges instead of rewriting the whole app at once. |
| 14 | 4. Use `wcf` or `entity-framework6` when the legacy app depends on those subsystems rather than flattening them into generic web work. |
| 15 | 5. Be careful with guidance copied from ASP.NET Core because middleware, DI, and hosting assumptions do not transfer directly. |
| 16 | 6. Validate in an environment that resembles real IIS and configuration transforms. |
| 17 | |
| 18 | ## Deliver |
| 19 | |
| 20 | - practical maintenance guidance for classic ASP.NET |
| 21 | - stabilized legacy behavior and modernization seams |
| 22 | - a migration path that avoids unnecessary risk |
| 23 | |
| 24 | ## Validate |
| 25 | |
| 26 | - classic and Core guidance are not mixed |
| 27 | - legacy runtime assumptions are preserved deliberately |
| 28 | - migration steps are incremental and testable |
| 29 | |
| 30 | ## References |
| 31 | |
| 32 | - [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 |
| 33 | - [Maintenance Patterns](references/patterns.md): stabilization and maintenance patterns for legacy ASP.NET code, including abstraction layers, testing seams, and deployment practices |
People who liked this also viewed
6 picksType
- hyperframes-cliUse the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, SkillsJul 2026
- request-refactor-planSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- analyze-projectRigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrSkillsMay 2026
- explore-codeRigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated braSkillsMay 2026
- ubiquitous-languageSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- scaffold-exercisesSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
