Thank you for the prompt support Awais. Please see below replies to your questions.
Are you seeing some exception messages? What are they? Yes, “At most 4 elements (for any collection) can be viewed in evaluation mode.”
In case of Aspose.Words, you can verify if the license is properly set by using the following code: No, we don’t have the ability to change the code in this use case. We are using our Aspose product in a Microsoft solution that includes uses compiled code, so we are not able to make any code edits. If setLicense cannot find a valid ‘paid’ license, does it throw an error or just apply the watermark and treat the failure as if it found a trial license?
For example, have you tried including the License file as an Embedded Resource? We don’t know if it’s set up in this way and do not have the ability to make this change. We have gone through the exercise of redeploying the apps with the new license and even tried removing the license file from the azure site altogether and restarting the service and we still have limited functionality.
We only have the ability to swap out the files in the solution—it is already compiled so we don’t have the ability to rework the solution or recompile the code to include the license as an embedded resource. We were instructed to add our own license to the solution. Initially we added a trial license, then we re-deployed with a full license. Even when we remove the license from the solution altogether, we still get the trial watermark.