Skip to main content

Delivery for C# and .NETs

.NET delivery is how an application gets from your machine to users. It covers publishing in framework-dependent or self-contained form, packaging libraries as NuGet packages, containers, versioning, and automated pipelines that build, test and release. The aim is a repeatable release that behaves the same in every environment.

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

What to learn in Delivery

Delivery interview questions

What is the difference between framework-dependent and self-contained deployment?

A framework-dependent app needs the .NET runtime already installed on the target and produces a smaller output. A self-contained app bundles the runtime, so it runs on machines without .NET but is larger and must be updated by redeploying.

What does semantic versioning communicate?

A version of major.minor.patch signals compatibility: a patch fixes bugs, a minor adds features without breaking callers, and a major may break existing code. Consumers of a NuGet package use it to decide how risky an upgrade is.

Where Delivery fits in the C# and .NET roadmap

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

Back to the full C# and .NET roadmap