Switch to the modern License.LicenseKey = "..." method. If you must use a license file, ensure the file path is correct. Part 7: Best Practices for Managing IronPDF License Keys Do Not Hardcode Keys in Source Control Never commit your license key to public repositories (GitHub, GitLab). Use secrets managers or environment variables . Rotate Keys Periodically If a developer leaves your team, you can invalidate their key from the Iron Software account portal and generate a new one. Separate Development and Production Keys You can generate multiple license keys under one account. Use a trial key for local development and your paid key for staging/production. This prevents accidental leakage of your production key. Automate Validation in CI/CD Pipelines In GitHub Actions or Azure DevOps, store your license key as a secret and inject it at runtime:
string key = config["IronPdf:LicenseKey"]; IronPdf.License.LicenseKey = key; ironpdf license key
using Microsoft.Extensions.Configuration; using IronPdf; var config = new ConfigurationBuilder() .AddJsonFile("appsettings.json") .Build(); Switch to the modern License
- name: Run IronPDF Tests env: IRONPDF_LICENSE: ${{ secrets.IRONPDF_LICENSE }} run: dotnet test Add this to your application startup logs: Use secrets managers or environment variables
{ "IronPdf": { "LicenseKey": "IRONPDF.MYCOMPANY.2023.ABCD1234EFGH" } }