ASP.NET Core Web API：为何继承ControllerBase而非Controller？

Great question! This is a super common point of confusion when you're getting started with ASP.NET Core Web APIs—let's break down the key reasons clearly:

• Controller includes MVC view-related baggage you don't need
  The Controller class actually inherits from ControllerBase under the hood, but adds extra functionality specifically for MVC (Model-View-Controller) applications, like view engine integration, the View() method for returning Razor views, and other UI-focused utilities. Since Web APIs typically return data formats like JSON or XML (not HTML views), all that view-related stuff is dead weight—using ControllerBase keeps your API controllers lean and avoids unnecessary dependencies.

• ControllerBase is purpose-built for APIs
  ControllerBase is designed exclusively for building HTTP APIs. It includes all the core features you need for API development:

  • Built-in support for returning HTTP status codes (like Ok(), NotFound(), BadRequest())
  • Integration with the [ApiController] attribute for automatic model validation and route inference
  • Access to HTTP context, request/response details, and dependency injection services
    All of this is tailored to API workflows, without any of the MVC view distractions.

• Reduces cognitive load and accidental mistakes
  If you use Controller, you'll have access to MVC-specific methods that don't make sense in an API context (like View() or PartialView()). This can lead to accidental misuse—for example, calling View() when you meant to return a JSON payload. Sticking with ControllerBase keeps your controller's API surface focused on what matters for your API, making your code more maintainable and less error-prone.

As a quick note: the template controller you saw inherits from Controller because it's meant to work for both MVC and API scenarios out of the box. But for dedicated Web API projects, switching to ControllerBase (paired with the [ApiController] attribute) is the recommended practice—it's cleaner, more focused, and aligns perfectly with API development best practices.

内容的提问来源于stack exchange，提问作者ProfK