Framework-dependent deployment
A framework-dependent deployment publishes an application without bundling its runtime, which must be installed compatibly on the target system.
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.
- How it is used
- Deploys a built ASP.NET Core application when the target already provides the .NET 7 Runtime.
- How deep it goes
- Explains runtime dependency, portability, size tradeoffs, publishing, and Linux prerequisites, but defers detailed runtime installation.
- Examples
- Uses ExampleApp.dll, dotnet publish, and Linux hosting behind NGINX, Apache, HAProxy, or YARP.
- What you can do after
- Operate/configure a published application by installing its runtime, copying its output, running its DLL, and routing traffic to it.
Read how ASP.NET Core in Action, 3e explains framework-dependent deployment →
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.
- How it is used
- Deploys ASP.NET Core applications to servers that already provide a compatible .NET runtime.
- How deep it goes
- Defines package contents, benefits, compatibility risks, and IIS prerequisites without detailing publishing commands.
- Examples
- Uses an ASP.NET Core web API hosted by IIS with the ASP.NET Core Windows Hosting Bundle installed.
- What you can do after
- Operate/configure an ASP.NET Core API on IIS by preparing the required runtime and hosting components.
Read how Building Web APIs with ASP.NET Core explains 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.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.