Skip to main content

Delivery for ASP.NET Cores

ASP.NET Core delivery is getting an application from source code to a running service. It includes publishing a release build, creating a Docker image, setting environment-specific configuration, adding health checks and logging, and deploying through a CI/CD pipeline to a host such as a VM, container platform or cloud service.

Stage: Quality and Delivery · Part of the ASP.NET Core roadmap · Last reviewed 19 November 2026

What to learn in Delivery

Delivery interview questions

Why use a multi-stage Dockerfile for .NET?

The first stage uses the large SDK image to restore and publish the app, and the final stage copies only the published output onto the smaller ASP.NET runtime image. The result is a smaller, safer image without compilers or source code.

What is a health check endpoint for?

A health check endpoint reports whether the app is able to serve requests, optionally checking dependencies like the database. Load balancers and orchestrators such as Kubernetes call it to decide whether to route traffic to an instance or restart it.

Where Delivery fits in the ASP.NET Core roadmap

Delivery belongs to the Quality and Delivery stage (advanced level). Ship.

Back to the full ASP.NET Core roadmap