Setting License fails

Aspose.Total Product Family
1

We have an applications that uses Aspose.Total. The license is set as embedded Resource. After compile, the application runs fine.

Then the Application is ran thru the Crypto Obfuscator For .Net 2015 program to combine all .net assemblies and compress and obfuscate the application.

Then we run the obfuscated exe and it fails because it can not find the license file.
I have tried the set license with and without the assembly name.

Is there a way to get the license to work in this case?


2

Hi Lisa,


Thank you for contacting support. We need to investigate this scenario. Please spare us a little time. We’ll get back to you soon.

3

Thanks for your reply. I’ll be waiting.

4

Hi Lisa,


Thank you for being patient. We managed to replicate the said error on our side. Please list down all your Aspose library names which you have referenced in your application project.

5

The current application uses Aspose Imaging. I also have another application that uses all except Aspose OCR

6

Hi Lisa,


Thank you for being patient. We have logged investigations under ticket ID’s WORDSNET-14154, CELLSNET-44732, DIAGRAMNET-51012, THREEDNET-210 and PDFNET-41405 for Aspose APIs Aspose.Words, Aspose.Cells, Aspose.Diagram, Aspose.3D and Aspose.Pdf respectively. We’re logging investigations for remaining Aspose for .NET APIs. We’ll share ticket ids soon.

7

Hi Lisa,


Thank you for being patient. We have also logged investigations under ticket ID’s SLIDESNET-37800, IMAGINGNET-2072 and BARCODENET-36326 for Aspose APIs Aspose.Slides, Aspose.Imaging, and Aspose.BarCode respectively. We’ll keep you informed regarding any available updates.

8

Hi Lisa,


Thank you for being patient. Our product teams have completed their analysis and come to the conclusion that they won’t fix this issue. It’s not failed to set the license, but the Aspose DLLs were never loaded by the operating system, because the Crypto Obfuscator created a new folder “CryptoObfuscator_Output” and saves the obfuscated EXE into this folder, and all dependent DLLs were not copied to that folder. This can happen to any external dependencies, not relevant to the licensing system of Aspose. In order to fix this issue, just copy the DLLs used by this EXE manually to the CryptoObfuscator_Output folder.

We hope, this helps. Please let us know in case of any confusion or questions.

9

Sorry that I have not gotten back to you sooner. You are correct. During our testing on our new test machine, the directory was clean when we copied all files over. That’s when I got the error.

Now when I copied the executable to our processing servers it works. Because the missing dlls were already there.

I have recompiled the application and re-run the Crypto Obfuscator to include all the Dlls. Moved it to the test machine and to an empty directory on our processing machine. Both work fine.

I am so sorry for not catching this problem myself.

Thank you all for your Great Support!

10
Hi Lisa,

Thank you for the confirmation. It is nice to hear from you that the problem has been resolved. Please let us know in case of any further assistance or questions.