I have a new (renewed) Aspose.Cells.lic file, received via email, as usual. I followed earlier practice by simply replacing the expired license in the bin folder with the new one. Does not work. The application functions correctly, but I get the extra Evaluation Warning tab. I inform my distributor, who contacts you folks. You tell him to tell me "Please ask your customer to be sure that the license file has been installed/deployed per the instructions found here:" followed by a link. This link provides instructions to install the PRODUCT, not to copy-and-paste the LICENSE (which has always worked without issue for us).
I was also told by you people via this same email to get my support via this forum. I sure hope this is more helpful than the instructions that were apparently sent without actually reading the problem!
Sign me as extremely frustrated by having to take two hours to communicate a problem that took five minutes to pass along, and was still misunderstood..
Hi boeing wiebe,
We are sorry, your process was delayed.
Copying and pasting should work fine, I think, application will load it from the same path which is embedded inside it. Just make sure path is ok. This is the case only when your older license was working fine. Please restart your application.
If your older license is not working fine now, then it could be that you have made changes inside your code, that are using Aspose.Cells Api (s) before setting the license.
Another possible reason is that your license file is corrupt or invalid. For that case to check, you can send me a private email.
Another reason, I could think of that licensing code has broken in newer versions. What is the version of Aspose.Cells for .NET, you are using?
I did check the path. It has not changed. In fact, when I copied the new license back into the bin folder, everything worked fine, even though it has expired.
Thanks
Is your problem resolved now? Did you copy New License or Old License back to Bin folder?
I guess I was not clear. I was merely testing the old license. It works, but it is expired. That is why we purchased a renewal. But it’s the new license that is giving us the Evaluation Warning tab.
Ok, send it to me, I will test it. If there is any problem. I will ask development team to resolve it. And show me your code snippet. Though, I can write my own, but may be your code could give me some clue.
Make your post private while attaching. I can even make this thread private, if you are having difficulty.
Please also mention the version number of Aspose.Cells for .NET which you are using.
Hi,
Please refer to this document
Hi,
I can confirm, your new license file is ok because I have generated the workbook without any sheet. Kindly test it at your end by giving absolute path.
I will be sending you a reply via email, along with our DLL.
Our DLL has been sent. Just one more comment for now. Whatever it is that lies at the heart of this problem, it is not about the path. As I have stated, our old expired license works with the code that you were sent last week. The new one has the same code with the same path, and does not work.
Thanks.
Did you try your OLD DLL with NEW LICENSE? Let me know, if new license works with old dll or not.
I do not know why you would think that I have more than one DLL. I do not. I only have the one obtained when the product was first purchased. It’s the only one we have ever had. It works with the OLD license, but not with the NEW license.
Hi,
Thanks I have received your email with DLL of Aspose.Cells 4.5.0.0. I will soon test it and let you know.
Hi,
Your new license does not run with old dll 4.5.0.0. I have logged it as CELLSNET-23970.
Please note: If you want to keep using old dll, then you did not need to purchase any new license for it. Purchasing a new license is only done, when you need newer dlls.
Hi,
Furthermore, the valid product name is Aspose.Cells or Aspose.Total for the older Dll e.g v4.5.0.
So if you still want to use the older dll v4.5, please use old license. If you want to use the new license, please update the dll (latest) too.
Thank you.
Thanks for clearing up our confusion. There are a couple of other questions that arise out of this situation.
1. If we decide to use our old version (4.5.0) instead of purchasing the newer version, will we be able to get technical support if we have problems with it? Or do we have to have your most current version (5.2.x?) in order to get support?
2. If we do decide to use the new license (for 5.2.x) that we now have, how do we go about getting the matching DLL for it? What is the standard procedure?
Please advise.
Hi,
Thanks for sharing your concerns.
1) Yes, sure we can provide technical help regarding features or certain operations. But, mind you, if there is some bug or limitation in the older version and you found it, we cannot fix it or add/enhance new features in the older versions . The bugs are fixed based on the latest version of the product only.
2) Well, I think regarding matching Dll you mean a bug fixed or enhanced version. This kind of version is posted in the support forums here. You can use the fix for your requirements as long as you wish; it will behave like an official release. Moreover, it is to be noted here, our every next official release would include all the functionalities of the previous fixes (including all the intermediate versions till the next official release).
Hope, you understand now.
Thank you.
#1 - Understood. Thanks.
#2 - When I say matching DLL, I am not talking about an enhanced version. Today we have only one DLL fos Aspose.Cells. It's the one that works with the license for our old version (4.5.0). The new license that we have, that you tested and found to work just fine with your DLL, does not work for us with our DLL. That's the issue you wrote up. CELLSNET-23970.
If we decide to use our new license (5.2.x), we need a DLL that will work with it. How do we obtain one?
Hi,
I am afraid, that’s not possible; you will have to change your obsolete code to new code to make it work correctly. What were the issues in your old DLL that you had to purchase a license? And why do you want to change your old DLL if it is working fine?
Suppose, if you have some issues with your old DLL and you ask us to fix them, then those issues will be fixed in latest versions and you will still have to use latest versions. So, I will recommend, you should upgrade your code.
Also, you can use this forum to quickly convert your obsolete code if any to newer code by posting here.