How deeply does Building Web APIs with ASP.NET Core cover framework-dependent deployment?

Defines package contents, benefits, compatibility risks, and IIS prerequisites without detailing publishing commands.

Framework-dependent deployment

As explained in Building Web APIs with ASP.NET Core

A .NET publishing and deployment mode in which an application requires a compatible .NET runtime installed on the target system.

Framework-dependent deployment publishes an application that requires a compatible .NET runtime installed on the target system. The deployment package contains the application and third-party dependencies, but not .NET itself. section 12.1.5

This mode involves practical trade-offs:

Produces a small deployment bundle because the target machine supplies the .NET runtime. section 12.1.5
Uses the latest installed compatible runtime by default, including its security patches. section 12.1.5
Can reduce storage and memory use when several .NET applications share a hosting server. section 12.1.5
Depends on runtime compatibility; an older server runtime can prevent the application from starting, and runtime changes can affect stability. section 12.1.5

Running an ASP.NET Core API on IIS

Install IIS, then install the ASP.NET Core Windows Hosting Bundle. The bundle supplies the .NET runtime, ASP.NET Core runtime, and ASP.NET Core IIS module needed to run an ASP.NET Core web API with framework-dependent publishing. Restart IIS after installation. section 12.3.2

How Building Web APIs with ASP.NET Core covers it

Cover of Building Web APIs with ASP.NET Core

liveBook manning.com

Read Building Web APIs with ASP.NET Core on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

ASP.NET Core in Action, 3eA framework-dependent deployment publishes an application without bundling the .NET runtime, which must already be installed on the target machine.

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 Building Web APIs with ASP.NET Core. The section links point to the parts of the book it draws on.