migrating-mvc-controllers Skill
Migrates ASP.NET Framework controllers and action results to ASP.NET Core equivalents, covering both MVC (Controller) and WebAPI (ApiController) patterns. Use when upgrading controllers that return HttpResponseMessage, IHttpActionResult, use ApiController base class, use Request.CreateResponse(), ResponseTypeAttribute, Published by microsoft in upgrade-agent-plugins.
What is migrating-mvc-controllers Skill?
Migrates ASP.NET Framework controllers and action results to ASP.NET Core equivalents, covering both MVC (Controller) and WebAPI (ApiController) patterns. Use when upgrading controllers that return HttpResponseMessage, IHttpActionResult, use ApiController base class, use Request.CreateResponse(), ResponseTypeAttribute, Published by microsoft in upgrade-agent-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using upgrade-agent-plugins
Technical details
- Install or run with Copy skill directory
When to use migrating-mvc-controllers Skill
- Use it for developers using upgrade-agent-plugins.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/upgrade-agent-plugins
- Skill file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/web/mvc/migrating-mvc-controllers/SKILL.md
What it does
Migrates ASP.NET Framework controllers and action results to ASP.NET Core equivalents, covering both MVC (Controller) and WebAPI (ApiController) patterns. Use when upgrading controllers that return HttpResponseMessage, IHttpActionResult, use ApiController base class, use Request.CreateResponse(), ResponseTypeAttribute,
Skill instructions
Controllers and Action Results Migration Overview Migrate ASP.NET Framework MVC and WebAPI controllers to ASP.NET Core. The return type system changed completely between frameworks — HttpResponseMessage is gone, status code helpers differ, and the ApiController vs ControllerBase distinction changes request processing behavior. Wrong choices produce incorrect HTTP responses that compile but fail at runtime. Workflow Migration Progress: - [ ] Step 1: Inventory controllers and classify (MVC vs WebAPI) - [ ] Step 2: Change base classes and namespaces - [ ] Step 3: Rewrite return types and response helpers - [ ] Step 4: Apply [ApiController] attribute where appropriate - [ ] Step 5: Migrate async action patterns - [ ] Step 6: Convert child actions to ViewComponents - [ ] Step 7: Verify build and endpoint behavior Step 1: Inventory Controllers Classify each controller as MVC or WebAPI based on its base class and usage: | Signal | Classification | |--------|---------------| | Inherits ApiCont
Explore related resources
Frequently asked questions
What is migrating-mvc-controllers?
migrating-mvc-controllers is a open-source AI agent skill with Copy skill directory. Migrates ASP.NET Framework controllers and action results to ASP.NET Core equivalents, covering both MVC (Controller) and WebAPI (ApiController) patterns.
Who is migrating-mvc-controllers best for?
migrating-mvc-controllers is best for reusing agent instructions, scripts, and references.
How do I install migrating-mvc-controllers?
Install or run migrating-mvc-controllers using Copy skill directory. Check migrating-mvc-controllers for the latest setup command.
Is migrating-mvc-controllers actively maintained?
migrating-mvc-controllers may need a closer maintenance check before production use.
Auto-fetched from GitHub.
