liveBook · Manning

Self-contained mode

As explained in Building Web APIs with ASP.NET Core

A .NET publishing mode that packages the required .NET libraries and runtime with the application so the target system does not need them installed separately.

Self-contained mode packages the application with the .NET libraries and runtime it needs, so the target system does not need those components installed separately. This isolates the application from other .NET applications on a compatible hosting server. section 12.1.5

A self-contained deployment has these practical characteristics:

  • Includes the application runtime and .NET libraries in the production build. section 12.1.5
  • Produces a platform-specific executable; on Windows, the deployment includes an .exe file and a DLL containing the application runtime. section 12.1.5
  • Avoids requiring .NET components on the target system, unlike framework-dependent mode. section 12.1.5

How Building Web APIs with ASP.NET Core covers it

How deep it goes
Defines bundled components and output artifacts, but does not detail publishing commands or configuration steps.
Examples
Uses a production bundle containing a platform-specific executable and a runtime DLL, including a Windows .exe.
What you can do after
Evaluate deployment choices by distinguishing bundled-runtime deployment from target-installed-runtime deployment.
How it connects
Contrasts with framework-dependent deployment and connects to .NET runtime, .NET libraries, and publishing modes.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Building Web APIs with ASP.NET Core. The section links point to the parts of the book it draws on.