How deeply does ASP.NET Core in Action, 3e cover framework-dependent deployment?

Explains runtime dependency, portability, size tradeoffs, publishing, and Linux prerequisites, but defers detailed runtime installation.

Framework-dependent deployment

As explained in ASP.NET Core in Action, 3e

A framework-dependent deployment publishes an application without bundling the .NET runtime, which must already be installed on the target machine.

A framework-dependent deployment (also called a runtime-dependent deployment, or RDD) publishes an already-built ASP.NET Core application without bundling the .NET runtime. The target machine must already have the .NET 7 Runtime installed. In return, the deployment is smaller and can run on Windows, Linux, or macOS without recompilation. section 27.1.1

Deploy an RDD with these practical steps:

Publish the application, for example with dotnet publish --output publish --configuration Release. section 27.1.1
Install the .NET 7 Runtime and necessary prerequisites on the target server. section 27.3.1
Copy the published files to the server and run the compiled application with dotnet ExampleApp.dll. section 27.1.1 section 27.3.1
On Linux, optionally place NGINX, Apache, HAProxy, or YARP in front of the application and configure a separate process manager. section 27.3.1

A small published deployment

After publishing an application into a publish folder, copy that folder to a server with the .NET 7 Runtime installed and start the application with dotnet ExampleApp.dll. The published output includes the application DLL and additional files such as wwwroot. section 27.1.1

dotnet publish --output publish --configuration Release

Use the publishing command to create the deployment output rather than copying the development build folder. section 27.1.1

How ASP.NET Core in Action, 3e covers it

liveBook manning.com

Read ASP.NET Core in Action, 3e on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Building Web APIs with ASP.NET CoreA .NET publishing and deployment mode in which an application requires a compatible .NET runtime installed on the target system.

Compare how 2 books explain framework-dependent deployment →

Related concepts

self-contained modealternative to · 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 deploymentcontrasts with · A self-contained deployment packages an application with its required runtime and framework components so it runs without a separately installed runtime.
Windows publishing profilepart of · A Windows publishing profile is a Visual Studio deployment configuration that specifies how an application is published for a Windows target.
dotnet publishproduced by · dotnet publish is a .NET CLI command that compiles an application and prepares its dependencies and supporting files for deployment.

This explainer was generated by Manning's knowledge graph from the text of ASP.NET Core in Action, 3e. The section links point to the parts of the book it draws on.