|
|
Rank: Newbie
Groups: Member
Joined: 9/23/2010
Posts: 7
|
I have two separately purchased components in same site that won't play well together.
I am developing a website under contract for a firm using my developer edition EO.Web components.
The firm purchased the EO.Pdf components for one of their developers to also work on the site.
I had used a trial of the EO.Pdf to demonstrate the PDF to them, which was at version 2014.
They liked what they saw and purchased EO.Pdf 2015 today (12/4/15).
I added their EO.Pdf.dll to the bin folder and their runtime key info into Global.asax (as well as trying it in Page_load handler).
Note that I also have my EO.Web in the bin folder as well as my .licx file.
We are still getting the "Trial Version" watermark on the bottom of the rendered PDF.
It seems that the two separately licensed components cannot cohabitate.
I feel like i am out on a limb here with my contract since they spent the money...
I had submitted this through the Contact Us this morning , but hadnt heard anything,
and hoping that posting to the forum may help me to get out of this hot water quicker.
How can I resolve this?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
You won't be able to use your EO.Pdf 2015 license key with EO.Pdf 2014. If you can PM us the EO.Pdf order number, we can manually "downgrade" it to EO.Pdf 2014, then you can download a license key for EO.Pdf 2014. After that we can change it back to 2015.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 9/23/2010
Posts: 7
|
Not sure you understand.
I am using their purchased EO.Pdf version 2015 (File version 15.3.31.0) along with the runtime key they downloaded today.
These should work together, of course, but the question is, will they work simultaneously with my EO.Web and .licx file which is a separate license.
Not sure if I confused you or not, but I did say that I added their EO.Pdf.dll to the bin folder and their runtime key info into Global.asax.
So, to be clear, they purchased EO.Pdf 2015 and I have EO.Web 2014. Will they work together in same site?
Does this help? Thanks for the quick reply.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
Sorry that I didn't understand your scenario clearly. This would depends on what version of the DLL you are using for EO.Web. If you are using the same 15.3.31.0 version for EO.Web, then it is supported. In this case the most common scenario is your license key is not called. You can verify whether this is the problem by calling your license key in your Page_Load. If that removes the license watermark, then it's definitely the code in your Global.asax is not properly called.
If your EO.Web is from a different version, then it is not officially supported. The root of the problem is not that you can not mix up the license key. The root of the problem is you can not mix up DLLs from different versions in the same application. Even though in your case you are using different product, but internally they are really just one product because they share a lot of code with each other. Mixing different versions of DLL is not possible at all since the 2015 release since all products in 2015 share a single EO.Base.dll and it is not possible for you to have two different versions of EO.Base.dll in the same application. However even before 2015 this is still not supported --- it's just since 2015 we explicitly created a shared DLL so that we can prevent this from the begining. In this case you would need to update your code to use the 2015 version of EO.Web. I noticed that you already have EO.Web license for the 2015 version. So this should not cost you anything.
Hope this clears it up. Please feel free to let us know if you still have any questions.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 9/23/2010
Posts: 7
|
Excellent Response!
That is perfectly clear. I appreciate it.
Yes, I do have the 2015 version of EO.Web. I have been a supporter of your products since 2010. Love 'em.
Problem is, the company network I must work in has tightened their security and I just happened to have the
2014 version here when they implemented it, and it's a pain to even get a DLL inside. So I stayed with the EO.Web 2014.
Now that I know what the problem is, I will figure out a way to get the resources I need inside their network one way or another.
Security is a good thing, but gets in the way sometimes even when you wear a white hat.
I'll get my latest version into the site and I'm sure everything will be fine.
You folks continue to have the best products and support of any component developers out there.
Keep up the good work, and I'll continue to recommend you whenever possible.
Cheers!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Excellent! Thank you very much for the compliment. Please feel free to let us know if there is anything else.
|
|