Welcome Guest Search | Active Topics | Sign In | Register

Issue with rendering licensing for EO.PDF in Console Application Options
IT Procurement
Posted: Tuesday, March 15, 2016 7:05:53 AM
Rank: Newbie
Groups: Member

Joined: 3/15/2016
Posts: 2
Hello

We have bought a license for EO.PDF's HTML to PDF converter for DotNet. In your instruction to add a licensing key, you are mentioning that EO.PDF.Runtime.AddLicense() code should be added in Global.asax in Application_Start handler.
This works perfectly fine if I am using a web application. But I am trying to use a Console Application to generate the PDF and it is failing to read the Licensing key from MVC web application. Can you please suggest the solution for this?
eo_support
Posted: Tuesday, March 15, 2016 8:37:46 AM
Rank: Administration
Groups: Administration

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

You would just call it before you call anything else in our library. The reason that we recommend you call it in Application_Start for a Web application because that's the first piece of code ASP.NET runs for your application. As such the key is to call the license code before anything else.

Thanks!
IT Procurement
Posted: Tuesday, March 15, 2016 11:59:40 AM
Rank: Newbie
Groups: Member

Joined: 3/15/2016
Posts: 2
I tried to do this as a very first thing in Main() but it is not setting EO.Pdf.Runtime.b in Console application.
However using Global.asax it can successfully set EO.Pdf.Runtime.a and EO.Pdf.Runtime.b configurations. This issue is blocking us from publishing the site therefore we really appreciate your quick response.
eo_support
Posted: Tuesday, March 15, 2016 12:06:09 PM
Rank: Administration
Groups: Administration

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

Please check whether your DLL version matches your license key version. You have a license for EO.Pdf 2015 and you can get license key for both 2015 version and 2016 version (because we include free one year subscription). The current version you download from our download page is 2016 version. So if that's the version you use, then you will need to go to your license key page to get 2016 license key. To check which version you are currently use, check the version any EO DLL. If it has a major version number of 15, then it's 2015 release. If it has a major version of 16, then it's a 2016 release.

Thanks!


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.