We have the following C# code:
Aspose.Words.License license = new Aspose.Words.License();
license.SetLicense(“Aspose.Total.NET.lic”);
The code worked. We renewed our license this year, downloaded the file, and got the error:
“Invalid license signature. Please make sure the license file was not modified.”
The license was not modified at all. If I remove the Set License command, the code works, but adds the “Evaluation use” watermark at the top of the files. The only noticeable difference between this license file and our previous license file is the length of the signature node, which is considerably longer in the new file.
If I switch back to the old license file, everything works normally.
We are experiencing this problem with both Aspose.PDF and Aspose.Words.
Please let me know if you have any questions or if there’s any other information I can provide.
@Stan.Shaw,
It appears that you are using an older version of the Aspose.Words and Aspose.PDF APIs with your new license. Could you kindly confirm which versions of Aspose.Words and Aspose.PDF APIs you are currently using? Please note, we have improved licensing mechanism. Newer licenses are signed with SHA256, while older licenses were signed with SHA1. Unfortunately, a SHA256 license cannot be used with older API versions (typically those older than 2-3 years).
To address this, you may continue using your older license with the older API versions and the new license with the newer API versions—this approach will always work seamlessly. Alternatively, you have the option to request a SHA1-encoded license (free of charge) from the Aspose.Purchase section or Sales category. This SHA1 license will be compatible with both older and newer versions of the Aspose (.NET) APIs.
Thank you very much for the quick reply. We will continue to use our old license file.
@Stan.Shaw,
Alright. If you have any additional questions or comments, please don’t hesitate to reach out to us again.