Missing assemblies

Like many others we are having trouble making use of your product because of the assembly problems, getting errors like this: Could not load file or assembly 'Aspose.Font

There are several ways that this could be resolved.

If you provided an assembly resolver that could be added to AppDomain.CurrentDomain.AssemblyResolve, this should solve the problem.

If you provided the full Aspose.Font and other assemblies, that would solve the problem.

If you provided only a stub version of Aspose.Font and other assemblies, that might solve the problem.


This problem makes this product very hard to integrate into certain systems. Please let us know when a fix will be available. Thank you.

Hi Really,


Thanks for contacting support.

We are aware that the issue occurs due to specific way IIS handles assembly references when the assembly in installed in GAC. We already have a ticket PDFNET-42106 in our issue tracking system for this issue. The product team is investigating the issues and as soon as we have some definite updates regarding the resolution, we will let you know. Please be patient and spare us little time. We are sorry for this inconvenience.

Best Regards,

We have the same issue on Aspose.pdf 17.3.0.0


Any ETA on the resolution?

We will be deploying out to customers’ GACs over the next few days. We will delay our deployments, but if it is going to take more than 2 weeks, then we will need to use an older version of Aspose.pdf.

Hi Chris,


Thanks for contacting support.

The product team is working on fixing earlier reported issue and we hope to get it resolved in next release of Aspose.Pdf for .NET 17.5 which is planned to release by next week. As soon as the new release becomes available, we will let you know.

Any news on the 17.5-Release?

Our customer is waiting for a release of our software, but we have to wait until this bug is fixed.

Hi Chris,


Thanks for your patience.

We plan to release the version by the end of this week or early next week. However as soon as it becomes available, we will let you know. Please be patient and spare us little time. We are sorry for this inconvenience.

Hi Nayyer


Any updates on the release date? And, what are the chances that this issue will not be resolved in the next (17.5) release?

Thanks

Hi Chris,


Thanks for your patience.

The product team is performing unit testing on new build and if everything goes fine, we plan to publish it within this week. So far we have targeted the earlier reported issue for current release and will keep you updated with the release status.

Hello,

since you posted your reply 1,5 weeks ago without a new release and in my test scenario the problem still exists - when will you solve the problem & release a new dll?
It is urgend!!

Kind regards,
Bea

Hi Bea,


Thanks for your patience and sorry for the delayed response.

I am afraid due to some technical limitations/difficulties, the earlier reported issue could not be resolved. However the team is working on fixing this issue and as soon as we have some updates regarding it’s resolution, we will let you know.

Meanwhile I have also shared your concerns with product team. Please be patient and spare us little time. We are sorry for this inconvenience.

Hello,


Thanks for your patience.

We are pleased to share that the issue reported earlier as PDFNET-42106 is resolved in latest release of Aspose.Pdf for .NET 17.6. Please try using the latest release and in the event of any further query, please feel free to contact.