Mixing Major Versions of IronPDF, IronOCR, and IronBarcode

Why It Fails

Every Iron Software product is built on a shared internal architecture, and its assemblies and dependencies are version-aligned across the suite. Each product assumes compatibility only with other products of the same major version, so mixing versions can surface several problems:

• Assembly binding conflicts
• Runtime errors
• Unexpected behavior

The libraries are designed to run together as a suite, not as independently versioned packages.

Solution

Use the same monthly version of every Iron Software library in a project. A correctly aligned set looks like this:

IronPDF v2025.5.x
IronOCR v2025.5.x
IronBarcode v2025.5.x

If your project already pins mismatched versions and you want to align them:

1. Upgrade through NuGet: bring every Iron Software library to the same monthly version.
2. Review the changes first: check the changelog and any API differences between versions before upgrading, so a version bump doesn't break existing calls.