Skip to content

ASP.NET Core

The web framework. Hosting, transports, middleware, DI, configuration, API surface (Minimal APIs and OpenAPI), routing, caching, rate limiting, error handling, and modern .NET 9 additions like MapStaticAssets.

Topics (canonical order)

Why this order

Hosting → background work → transports → pipeline → DI → config establishes the runtime substrate before introducing API surface (Minimal APIs / MVC / Razor). API surface comes before routing/caching/rate-limiting because those concepts apply across all API styles. ProblemDetails / globalization / static-assets / OpenAPI cluster at the end as cross-cutting concerns.

Cross-references