Dependency "Aspose.Imaging" and "Aspose.Drawing"

Aspose.PDF Product Family
1

We have code in our app that tries to load all referenced assemblies. This code fails after integrating “Aspose.PDF":

System.IO.FileNotFoundException: Could not load file or assembly 'Aspose.Drawing, Version=24.2.0.0, Culture=neutral, PublicKeyToken=716fcc553a201e56'. Das System kann die angegebene Datei nicht finden.
File name: 'Aspose.Drawing, Version=24.2.0.0, Culture=neutral, PublicKeyToken=716fcc553a201e56'

The german part of the error translates to “The system cannot find the file specified”.

See attached sample: AsposePDFDependencies.zip (7.9 KB)

Bonus question: the parent assembly “Aspose.Imaging” is loaded, but apparently not from a disc location, as the property “Assembly.Location” is null. Where does it come from - is it embedded in “Aspose.PDF”?

It works if I add the packages “Aspose.Drawing” and “Aspose.Imaging”.

I ran into a similar issue with Aspose.Cells.GridDesktop - maybe it is related: GridDesktop: Dependency "HtmlTextWriter"

Do you have any suggestions? We could simply ignore “Aspose.Imaging” in our preload code if you can confirm that it is safe to do so.

3

@wknauf
I investigated a bit, issue was reproduced
As I know, the suggestion of Aspose.Imaging embedded in Aspose PDF is correct so it seems that you can ignore it
I tried for comparison to change Aspose PDF to Aspose PDF Drawing that has embedded Drawing solution, it fails on Imaging and Newtonsoft.Json.
Anyway, I’ll add task for development team for this as I can find no other solution for you right now

4

@wknauf
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): PDFNET-58253

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

5

Just want to ask for an update. Do you plan to change anything, or is our temporary workaround (ignore “Aspose.Imaging” in our preload code) a permanent solution?

6

@wknauf
I looked at the information in the tracker - the task is assigned to the developer, but research on it has not yet been conducted.

Created tasks are solved in the order they are received, taking into account priorities.
The highest priority is for tasks with paid support, followed by tasks from users who have purchased a license.
The time it takes to solve problems can also vary. Therefore, unfortunately, it is not even possible to give ETA.

7

JFYI: my company has bought a license, but my forum account uses a different mail address.

8

I have made the appropriate changes to the ticket and written your request to the developers. Perhaps this will speed up the work on this task.

9

It is again time to ask for an update :wink: : Do you plan to change anything, or is our temporary workaround (ignore “Aspose.Imaging” in our preload code) a permanent solution?

10

@wknauf
Currently issue is assigned to developer with no further updates
But interestingly enough I checked with your application on 25.2 version and it seems that problem with Imaging is gone - although there’s still issue with Aspose Drawing
could you check if the issue with Imaging still persists on latest version?
Here’s result with skipping Aspose Drawing
result_with_drawing_ignore.png (10.2 KB)

11

@ilyazhuykov “Aspose.Imaging” still shows the same strange behavior for me with the current version: it is not loaded from a disc location, my sample prints the text “=>found at” followed by the value of “Assembly.Location”, which is empty for this assembly. So I assume it is provided from somewhere else?

Do you load this assembly with a custom assembly resolver and it is bundled in “Aspose.Pdf”?

12

@wknauf
It’s inbuilt in Aspose Pdf, yes
Maybe I just misremembered that it caused error in log
There was a discussion about resolving the issue with Aspose Imaging team , seems that nothing changed then
I’ll try to ask development team directly , hopefully there will be some updates.
In any case I’ll write you back tomorrow and inform about current state of issue

13

@wknauf , Unfortunately, the answer is that currently there’s no plans to fix this issue in nearest future.

14

No problem, I have a workaround on my side. I created this issue just because I wanted to verify whether there is really something missing or whether it is safe to ignore this error.
So you don’t need to fix anything if you are sure that there is no problem :wink: .

15

@wknauf , Well, currently there’s no known consequences as Imaging and Drawing are extensions that built in Aspose Pdf so there shouldn’t be concerns on this part at least

16

OK, so we could close this question as “resolved”.

1 Like