Evaluation Warning message on Aspose.Cells license

Aspose.Cells Product Family
1

Hello,

we are getting an evaluation warning message when using the recently purchased license file. I’ve attached the error screenshot below. We are testing the license on our staging site instance before launch to production. Is there an issue with the license?

Thanks

image (13).png (32.1 KB)

2

@TimeSquaredConcierge

It sounds like you’re encountering an evaluation warning message despite having a purchased license file. Here’s how to resolve this issue:

Cause: The warning may arise from an incorrectly configured license file or issues with how the license is being applied in your code.

Solution: Follow these steps to troubleshoot:

  1. Verify License File: Ensure that the license file is correctly named and located in the expected directory. The file should not have any additional extensions (like .xml).

  2. Set License in Code: Make sure you are setting the license in your code before using any Aspose.Cells classes. Here’s a sample code snippet to set the license:

    License license = new License();
license.setLicense("path/to/your/Aspose.Cells.lic");

  3. Check for Multiple Instances: If you are using multiple Aspose products, ensure that you are setting the license for each product separately.

  4. Environment Check: If you are testing on a staging site, confirm that the environment is correctly configured to access the license file.

  5. License Expiry: Double-check that your license has not expired and is valid for the version of Aspose.Cells you are using.

Next Steps: After following these steps, if you still encounter issues, please provide additional details about your setup, and we can explore further options to resolve the problem.

Thank you for your patience, and I look forward to helping you get this resolved!

3

@TimeSquaredConcierge,

Could you clarify which version of Aspose.Cells for .NET you are currently using with your new license? Additionally, ensure that the licensing code is properly added/implemented and executed at the very beginning of the application life cycle, it should be only once and before calling any other Aspose.Cells APIs. For guidance, you can refer to the Licensing documentation. It seems the licensing code might not have been executed correctly, or you may be using an outdated version of Aspose.Cells.

4

The version of the license is:

3.0

we have confirmed that the licensing code was properly added. Prior to this we had 2.2 installed and purchased our own license for usage instead. This license worked fine with no issues.

5

@TimeSquaredConcierge,

Apologies for the confusion, but I am inquiring about the API/library version of Aspose.Cells, not the license version. Could you kindly provide the details regarding that?

6

It looks like we are using:

it seems we need to update to the latest version then apply the license. we will work on this and reach back out if there are any issues.

Thanks

7

@TimeSquaredConcierge,

Sure, please try using latest version of Aspose.Cells with new license. If you encounter any issues, please reach out to us, and we will be glad to assist you soon.

8

@TimeSquaredConcierge

If you are using one old version of Cells component with 2.2 version of license, the old license you used may be signed with SHA1, while your newly purchased one is signed with SHA256.

You may request an updated (new) license (in the purchase section) that should be signed with SHA1 if you need to stay with old version of Cells component. However, new version of the component is strongly recommended because there are many bug fixes and enhancements added, and if you find bugs with the component, we can only provide fixes based on latest version.

9

to add to what was mentioned, is there an approach to keep our component which is:

then update the recently purchased license to support this component?

we ran a package update and its a huge gap between versions (25.7.0 vs 4.8.0.0) which is throwing numerous errors with our current workflow

10

@TimeSquaredConcierge ,

When upgrading to the latest Aspose.Cells APIs (v25.7.0), you may encounter compile-time errors. This is due to numerous improvements and new features that have been introduced over the years to enhance the robustness and functionality of Aspose.Cells. If you are currently using an older version (e.g., 4.8.0.0), you will need to adjust your existing code to align with the updated APIs.

We kindly recommend reviewing the Aspose.Cells for .NET Documentation and exploring the API Reference Pages for detailed guidance.

Upgrading to the latest version is highly beneficial, as it provides access to new features, enhancements, bug fixes, and improved performance over time. To ease the transition, you might consider gradually updating your application to incorporate the newer APIs while maintaining your current setup in parallel. Once the migration is complete, you can replace the older application with the updated one that utilizes the new license.

Please note that your new license will not be compatible with the older version of the API (4.8.0.0) because it is signed with SHA256. If you wish to continue using the older version, there are two possible options:

  1. You can use your older license with the older version (4.8.0.0), which will always work seamlessly. You can use new license with new version of the API.
  2. Alternatively, you may request a free updated license signed with SHA1 by reaching out to the Sales Team. This license would be compatible with both older and newer versions of Aspose.Cells.

If you need any further assistance with upgrading to the latest APIs, please don’t hesitate to let us know. We are here to help.

11

Thanks, I will reach out out to the Sales Team for a free updated license and will reference this conversation.

12

@TimeSquaredConcierge
You are welcome. If you have any questions, please feel free to contact us at any time.