aspnet-mvc5-webapi2

Automate ASP.NET MVC 5 and Web API 2 implementation in .NET Framework projects.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/FerranGuardia/claude-autonomous-setup --skill aspnet-mvc5-webapi2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspnet-mvc5-webapi2
Source: https://github.com/FerranGuardia/claude-autonomous-setup/tree/main/skills/backend/aspnet-mvc5-webapi2
Command: npx skills add https://github.com/FerranGuardia/claude-autonomous-setup --skill aspnet-mvc5-webapi2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear, pattern-driven blueprint for implementing ASP.NET MVC 5 and Web API 2 on the .NET Framework, avoiding ASP.NET Core patterns and ensuring correct separation of concerns.

Core Features & Use Cases

  • Clear separation of Web API controllers and MVC controllers within legacy projects.
  • Deterministic routing: Web API routes are configured before MVC routes to prevent API paths from being swallowed.
  • Comprehensive guidance on configuration, DI, filters, and error handling for stable, maintainable apps.
  • Use cases include enterprise applications migrating from older frameworks or maintaining large .NET Framework projects with strict routing rules.

Quick Start

Register WebApiConfig before RouteConfig to ensure api/ endpoints resolve correctly.

Frequently Asked Questions about aspnet-mvc5-webapi2

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why do my ASP.NET Web API 2 routes get swallowed by MVC 5 controllers?

ASP.NET Web API 2 routes get swallowed when RouteConfig is registered before WebApiConfig. Register WebApiConfig first to ensure api/ endpoints resolve correctly and prevent MVC 5 from intercepting API paths.

How do I configure dependency injection for legacy ASP.NET MVC 5 and Web API 2 projects?

Configure dependency injection in legacy ASP.NET MVC 5 and Web API 2 projects by applying pattern-driven blueprints. This enforces proper separation of concerns, global configuration, and maintainable project structure for .NET Framework enterprise apps.

Can I use ASP.NET Core patterns when maintaining .NET Framework Web API 2 applications?

No, you should not use ASP.NET Core patterns when maintaining .NET Framework Web API 2 applications. This guide avoids ASP.NET Core patterns, providing a clear blueprint for proper separation of concerns specific to legacy .NET Framework projects.

What is the best way to separate MVC 5 controllers and Web API 2 controllers in a legacy enterprise app?

The best way to separate MVC 5 and Web API 2 controllers in legacy enterprise apps is using deterministic routing configurations. This pattern-driven approach ensures clear separation of concerns and stable, maintainable project structure.

How do I set up global filters and error handling for ASP.NET MVC 5 applications?

Set up global filters and error handling for ASP.NET MVC 5 applications through comprehensive configuration guidance. This enforces stable, maintainable apps by applying proper routing order, dependency injection, and global configuration patterns.