Welcome Guest Search | Active Topics | Sign In | Register

EO.PDF License Options
Mike
Posted: Friday, March 14, 2025 10:56:26 AM
Rank: Member
Groups: Member

Joined: 11/7/2013
Posts: 15
Just received our license for EO.Pdf 2024. After applying the add license and testing, the following error message is displayed

License data provided by AddLicense is invalid

I am using the EO.Pdf 2018 assembly thinking the license was backward compatible. We have not updated our EO.Web or EO.Pdf to version 2024/2025 yet. Do we need to do this to get the EO.Pdf functionality?

Thanks,
Mike
eo_support
Posted: Friday, March 14, 2025 11:12:46 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,298
Hi,

Each version uses a different license key and the license key version and the DLL version must match. So for example, you will get this error message if you try to use your EO.Pdf 2018 assembly with EO.Pdf 2024 license key. As such if you use EO.Pdf 2024 license key, then you must update your DLLs to 2024 version. If you use EO.Pdf 2025 license key, then you must update your DLLs to 2025 version.

Thanks!
Mike
Posted: Friday, March 14, 2025 11:19:07 AM
Rank: Member
Groups: Member

Joined: 11/7/2013
Posts: 15
Hi,

Thanks for the reply. Do the licenses work independently of each other? Can I continue to use EO.Web assemblies for 2018 and update EO.Pdf assemblies for 2024?

Thanks,
Mike
eo_support
Posted: Friday, March 14, 2025 11:47:25 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,298
Yes. They work independently within the same application. So for example, you can have application A using v2018 assemblies and v2018 license key, and then application B using v2024 assemblies and v2024 license key.
Mike
Posted: Friday, March 14, 2025 4:12:45 PM
Rank: Member
Groups: Member

Joined: 11/7/2013
Posts: 15
Hi,

Been working with this most of the afternoon. As expected, the update to EO.Pdf forced an update to EO.Base to version 2025. This in turn forced update to EO.Web 2025, but I only have the 2024 version which I added to no avail. Unless I am really missing something, I'm not able to mix the versions.

My original intention was to keep EO.Web at 2018 and add EO.Pdf 2025 just by updating the assembly and adding a EO.Pdf.Runtime.AddLicense statement to the Global.asax.

Is there a step by step I can follow to get this working?

Thanks,
Mike


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.