migrating-mvc-filters Skill
Migrates ASP.NET MVC global filters (GlobalFilterCollection, HandleErrorAttribute, FilterConfig) to ASP.NET Core exception handling middleware and filter pipeline. Use when upgrading MVC apps that register filters via GlobalFilters.Filters.Add(), have a FilterConfig.cs, use HandleErrorAttribute, or need to convert cust Published by microsoft in upgrade-agent-plugins.
What is migrating-mvc-filters Skill?
Migrates ASP.NET MVC global filters (GlobalFilterCollection, HandleErrorAttribute, FilterConfig) to ASP.NET Core exception handling middleware and filter pipeline. Use when upgrading MVC apps that register filters via GlobalFilters.Filters.Add(), have a FilterConfig.cs, use HandleErrorAttribute, or need to convert cust 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-filters 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-filters/SKILL.md
What it does
Migrates ASP.NET MVC global filters (GlobalFilterCollection, HandleErrorAttribute, FilterConfig) to ASP.NET Core exception handling middleware and filter pipeline. Use when upgrading MVC apps that register filters via GlobalFilters.Filters.Add(), have a FilterConfig.cs, use HandleErrorAttribute, or need to convert cust
Skill instructions
ASP.NET MVC Global Filters Migration Overview Migrate GlobalFilterCollection-based filters from ASP.NET MVC to ASP.NET Core middleware and filter pipeline. ASP.NET Core replaces HandleErrorAttribute with UseExceptionHandler middleware because middleware runs earlier in the pipeline and catches errors from all middleware, not just controller actions. Workflow Track progress across these steps: Migration Progress: - [ ] Step 1: Identify main controller from routing - [ ] Step 2: Add exception handler middleware - [ ] Step 3: Add error action methods - [ ] Step 4: Create error views - [ ] Step 5: Convert custom filters - [ ] Step 6: Remove FilterConfig and GlobalFilters references Step 1: Identify Main Controller Determine the main controller name from routing configuration. Check Program.cs for route registration first, then fall back to RouteConfig.cs if the project hasn't been fully migrated. The default route typically maps to HomeController. This controller will host the error-handli
Explore related resources
Frequently asked questions
What is migrating-mvc-filters?
migrating-mvc-filters is a open-source AI agent skill with Copy skill directory. Migrates ASP.NET MVC global filters (GlobalFilterCollection, HandleErrorAttribute, FilterConfig) to ASP.NET Core exception handling middleware and filter pipeline.
Who is migrating-mvc-filters best for?
migrating-mvc-filters is best for reusing agent instructions, scripts, and references.
How do I install migrating-mvc-filters?
Install or run migrating-mvc-filters using Copy skill directory. Check migrating-mvc-filters for the latest setup command.
Is migrating-mvc-filters actively maintained?
migrating-mvc-filters may need a closer maintenance check before production use.
Auto-fetched from GitHub.
