migrating-mvc-httpcontext Skill
Migrates ASP.NET Framework HttpContext, Request, and Response usage to ASP.NET Core equivalents. Use when projects reference HttpContext.Current, HttpRequest.InputStream, HttpResponse.Write, HttpServerUtility, Request.ServerVariables, Request.Files, Response.End, Response.AddHeader, or ClaimsPrincipal.Current. Also tri Published by microsoft in upgrade-agent-plugins.
What is migrating-mvc-httpcontext Skill?
Migrates ASP.NET Framework HttpContext, Request, and Response usage to ASP.NET Core equivalents. Use when projects reference HttpContext.Current, HttpRequest.InputStream, HttpResponse.Write, HttpServerUtility, Request.ServerVariables, Request.Files, Response.End, Response.AddHeader, or ClaimsPrincipal.Current. Also tri 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
- Writing
- Writing use cases
Technical details
- Install or run with Copy skill directory
When to use migrating-mvc-httpcontext Skill
- Use it for writing.
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-httpcontext/SKILL.md
What it does
Migrates ASP.NET Framework HttpContext, Request, and Response usage to ASP.NET Core equivalents. Use when projects reference HttpContext.Current, HttpRequest.InputStream, HttpResponse.Write, HttpServerUtility, Request.ServerVariables, Request.Files, Response.End, Response.AddHeader, or ClaimsPrincipal.Current. Also tri
Skill instructions
ASP.NET MVC HttpContext and Request/Response Migration Overview Migrate HttpContext.Current, HttpRequest, HttpResponse, and HttpServerUtility usage from ASP.NET Framework to ASP.NET Core. The static HttpContext.Current accessor is removed in Core — all context access flows through dependency injection or controller base class properties. Response writing is async-only in Kestrel, and request reading APIs have changed types and behavior. Adapter precedence: If the aspnet-system-web-adapters skill is loaded, its guidance takes precedence over HttpContext.Current, Request Access, Response Access, and ClaimsPrincipal.Current sections during scaffold and migrate task phases. Workflow Track progress across these steps: Migration Progress: - [ ] Step 1: Inventory HttpContext usage patterns - [ ] Step 2: Eliminate HttpContext.Current - [ ] Step 3: Migrate request access patterns - [ ] Step 4: Migrate response access patterns - [ ] Step 5: Replace HttpServerUtility calls - [ ] Step 6: Migrate C
Explore related resources
Frequently asked questions
What is migrating-mvc-httpcontext?
migrating-mvc-httpcontext is a open-source AI agent skill with Copy skill directory. Migrates ASP.NET Framework HttpContext, Request, and Response usage to ASP.NET Core equivalents.
Who is migrating-mvc-httpcontext best for?
migrating-mvc-httpcontext is best for reusing agent instructions, scripts, and references, writing workflows.
How do I install migrating-mvc-httpcontext?
Install or run migrating-mvc-httpcontext using Copy skill directory. Check migrating-mvc-httpcontext for the latest setup command.
Is migrating-mvc-httpcontext actively maintained?
migrating-mvc-httpcontext may need a closer maintenance check before production use.
Auto-fetched from GitHub.
