frameworkdependent

Framework-dependent refers to software that relies on a separate framework component installed on the host system to run, rather than bundling the framework with the application package. In such deployments, the package contains the application code and its direct libraries, but not the framework itself; the framework is expected to be available globally on the machine at runtime.

In the .NET ecosystem, a framework-dependent deployment uses the shared framework installed on the machine, while a self-contained deployment bundles the runtime with the application. This distinction is common across other ecosystems as well, where the runtime or platform is provided separately by the operating system or a common runtime installation.

How it works: at launch, the application loads framework assemblies from the installed framework rather than from the application package. Version compatibility is important: the app requires a compatible framework version, and updates to the shared framework can affect behavior.

Advantages: reduced package size and faster deployments, since framework components are shared across multiple applications. A single framework installation can serve many apps, and updates to the framework can improve security and performance for all dependent software.

Disadvantages: dependency on a pre-installed framework makes the application less portable and can introduce version conflicts if the installed framework does not meet the app’s minimum requirements. Operators may need to ensure the correct framework version is present.

Use cases: framework-dependent deployments are common when disk space, centralized framework management, and consistency across multiple applications are priorities, and the target environment is controlled to guarantee the required framework is installed. See also self-contained deployment and runtime.