|
|
Rank: Newbie
Groups: Member
Joined: 1/2/2018
Posts: 3
|
I'm enhancing an older product. One that has never been run on Windows 10. But is now and fails on PDF creation. We are currently using EO.PDF version 4.0.41.2. It's quite evident we need to upgrade. This product also runs on .Net 3.5 and we can't necessarily upgrade the .Net version (customer requirements).
What is the current version of EO.PDF and do we have to upgrade our project's .Net Framework version?
If we do can we upgrade to another, older version (but newer than 4.0.41.2) that uses .Net 3.5 and runs on Windows 10?
Thanks
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi,
The current version runs on .NET 2.0 and above. So you do not need to upgrade your .NET version when you upgrade.
Since you have a quite old version (released in 2012) and we started support Windows 10 in 2015, which is 3 years ahead of yours but still almost 3 years old. So it doesn't make sense for you to update to that version at all.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 1/2/2018
Posts: 3
|
Continuing my upgrade question...
Are there any special steps in upgrading servers with the newest version of EO.PDF? Is it as simple as deploying the DLL with the website code?
In the source code there is the following...
EO.Pdf.Runtime.AddLicense (licenseKey);
Where licenseKey looks like a 352 character GUID.
Do we keep the current key, get a new one, or is the whole process different now?
Thanks.
I downloaded the latest code for EO.Total even though I'm just interested in EO.PDF. Updated my web project with the 4 necessary DLL's: EO.Base, EO.Pdf, EO.WebBrowser and EO.WebEngine. I am using my 2012 license. It fails. So I guess I will need a new one when we upgrade.
These 4 DLL's are all I will need to deploy to the web server then?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi, Yes. Those 4 DLLs are the core DLLs that you must deploy to your web server. A few other features are included in other DLLs (for example, if you use the WPF wrapper, then you will need EO.Pdf.Wpf.dll). You can see the complete list here: https://www.essentialobjects.com/doc/pdf/install/deploy.aspxYou will need to place a new order and then get a new license key for the new version. You would apply license key the same way but it will be a different license key. The main difference is that it now split into a few DLLs. This is due to the fact that we switched to a much newer Chromium based browser engine and we now share the same browser engine between different products. However all files are still xcopy distribution, so no additional setup is needed on the server side. Please feel free to let us know if you still have any questions. Thanks!
|
|