migrating-mvc-dependency-injection Skill
Migrates dependency injection configuration from ASP.NET Framework MVC and WebAPI projects to ASP.NET Core built-in DI or modernized third-party container integration. Use when upgrading projects that use DependencyResolver.SetResolver, config.DependencyResolver, custom IControllerFactory, custom IHttpControllerActivat Published by microsoft in upgrade-agent-plugins.
What is migrating-mvc-dependency-injection Skill?
Migrates dependency injection configuration from ASP.NET Framework MVC and WebAPI projects to ASP.NET Core built-in DI or modernized third-party container integration. Use when upgrading projects that use DependencyResolver.SetResolver, config.DependencyResolver, custom IControllerFactory, custom IHttpControllerActivat 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
- Research
- Research use cases
Technical details
- Install or run with Copy skill directory
When to use migrating-mvc-dependency-injection Skill
- Use it for research.
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-dependency-injection/SKILL.md
What it does
Migrates dependency injection configuration from ASP.NET Framework MVC and WebAPI projects to ASP.NET Core built-in DI or modernized third-party container integration. Use when upgrading projects that use DependencyResolver.SetResolver, config.DependencyResolver, custom IControllerFactory, custom IHttpControllerActivat
Skill instructions
ASP.NET MVC/WebAPI Dependency Injection Migration Overview Migrate DependencyResolver-based DI from ASP.NET MVC and WebAPI to ASP.NET Core's built-in IServiceCollection/IServiceProvider pattern, or modernize third-party container integration. ASP.NET Core has DI built into the framework — the DependencyResolver and IDependencyScope APIs no longer exist. Related skills: - To remove Autofac entirely and use built-in DI: see migrating-autofac-to-dotnet-di - To keep Autofac but modernize its integration: see integrating-autofac-with-dotnet Workflow Migration Progress: - [ ] Step 1: Inventory DI usage - [ ] Step 2: Map service registrations and lifetimes - [ ] Step 3: Register services in Program.cs - [ ] Step 4: Migrate or remove third-party container - [ ] Step 5: Migrate controller factory customizations - [ ] Step 6: Eliminate Service Locator usage - [ ] Step 7: Remove obsolete DI code - [ ] Step 8: Build and verify Step 1: Inventory DI Usage Search the project for these patterns to det
Explore related resources
Frequently asked questions
What is migrating-mvc-dependency-injection?
migrating-mvc-dependency-injection is a open-source AI agent skill with Copy skill directory. Migrates dependency injection configuration from ASP.NET Framework MVC and WebAPI projects to ASP.NET Core built-in DI or modernized third-party container integration.
Who is migrating-mvc-dependency-injection best for?
migrating-mvc-dependency-injection is best for reusing agent instructions, scripts, and references, research workflows.
How do I install migrating-mvc-dependency-injection?
Install or run migrating-mvc-dependency-injection using Copy skill directory. Check migrating-mvc-dependency-injection for the latest setup command.
Is migrating-mvc-dependency-injection actively maintained?
migrating-mvc-dependency-injection may need a closer maintenance check before production use.
Auto-fetched from GitHub.
