Don't Panic: ASP.NET Core Fundamentals

ASP.NET Core is the .NET framework for turning an HTTP request into useful application work and then returning a response before the browser, mobile client, or another service becomes impatient. It does this with a host, a server, a pipeline, and endpoints. That sounds like a committee designed it. In this case, the committee left you a usable map.

The host owns the runtime furniture: Kestrel, configuration, logging, dependency injection, middleware, and lifetime signals. Kestrel accepts the connection and creates an HttpContext, the per-request bundle containing the request, response, current user, selected endpoint, and request-scoped services. From there, the request enters middleware, which is code arranged around the next step. It can inspect the request, call onward, inspect the response on its return journey, or end the trip early. Static files and rejected requests are allowed to leave before meeting an endpoint. They have places to be.

Routing chooses an endpoint from the URL and HTTP method. The endpoint then binds request data into .NET values, checks declared input rules, applies authorization, and coordinates application services. These are separate questions. A value can have the right shape, a caller can have an identity, and the operation can still be forbidden or invalid for the current business state. Computers enjoy this distinction because it gives them several places to say no.

Order is the surprise waiting in the corridor. Middleware order is application behavior, not decoration. An exception handler can only contain failures from components it wraps. Authentication establishes identity before authorization decides access. A proxy in front of Kestrel may describe the original scheme and client address, but the application must trust only known proxies. Otherwise, an incoming header has promoted itself to a witness, which is not how evidence works.

Pick an endpoint model for the boundary you need. Minimal APIs fit focused HTTP services. Controllers add class conventions. MVC and Razor Pages render server HTML. SignalR handles persistent real-time connections, while Blazor builds interactive .NET interfaces. They share the same host and request machinery, so this is a choice of shape, not a choice of separate universes.

Next, read the Intro for the complete request flow and the Cheatsheet when you need the names and order close at hand. Use the Practice tab to make a route, middleware, scoped service, and result observable on a local host. The Quiz checks the boundaries that are easy to blur. The Reference tab is the route onward when the framework starts asking for exact configuration rather than a mental model.

Don't Panic: ASP.NET Core Fundamentals

Relevant careers