How to Add IronPDF to Installers

Publishing Methods: Learn more about .NET deployment

  • Self-contained: Includes the .NET runtime and libraries, as well as your application and its dependencies. Users of the application can run it on a machine that doesn't have the .NET runtime installed.
  • Framework-dependent: Includes only your application and its dependencies. Users of the application need to separately install the .NET runtime.

Publish Commands

Framework-dependent executable for the current platform:

dotnet publish
dotnet publish
SHELL

Framework-dependent executable for a specific platform:

dotnet publish -r <RID> --self-contained false
dotnet publish -r <RID> --self-contained false
SHELL

Tips
Replace <RID> with the Runtime Identifier of your target platform. For example, win-x64 for Windows 64-bit.

Framework-dependent binary:

dotnet publish
dotnet publish
SHELL

Self-contained executable:

dotnet publish -r <RID>
dotnet publish -r <RID>
SHELL

Tips
Again, replace <RID> with the specific Runtime Identifier for your target platform.

For more details, see .NET dotnet publish command and .NET fundamentals Single-file deployment and executable.

IronPDF Installer

Licensing

Distribution of your project requires a license including SAAS/OEM Redistribution.

You should apply the license key in your code as follows:

// Apply your license for IronPDF
IronPdf.License.LicenseKey = "YOUR_LICENSE_KEY";
// Apply your license for IronPDF
IronPdf.License.LicenseKey = "YOUR_LICENSE_KEY";
' Apply your license for IronPDF
IronPdf.License.LicenseKey = "YOUR_LICENSE_KEY"
$vbLabelText   $csharpLabel

Tips
Replace "YOUR_LICENSE_KEY" with your actual IronPDF license key.