Hello,
When trying to convert a Publisher file on GroupDocs.Conversion.NETFramework 26.3.0 it fails with Unable to load Aspose.PDF error.
This can be easily fixed by manually referencing the Aspose.PDF package - but I would expect all dependencies to be included with the main package?
Also - what are your current release plans? It always used to be monthly releases towards the end of the month - but looks like it’s quarterly now?
Thanks
@rthomas95
Thanks for reporting this. We’ve reproduced it — it’s a version-matching issue that only affects Publisher conversions on the .NET Framework build, which is why the “unable to load Aspose.PDF” error appears. We’ve logged it to be fixed in the package.
In the meantime, two options work:
- Referencing the Aspose.PDF package, as you found — perfectly safe to use.
- A lighter alternative: add this binding redirect to your app.config/web.config:
<dependentAssembly>
<assemblyIdentity name="Aspose.PDF" publicKeyToken="716fcc553a201e56" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-26.1.0.0" newVersion="26.1.0.0" />
</dependentAssembly>
On releases — you’re right, the cadence changed: monthly through 2025, then roughly quarterly from 2026 (26.1, 26.3). Our next planned release is 26.6, and we’ll aim to include the Publisher fix there. The workarounds above will keep you going until then.
1 Like
Hi Nikola,
That’s great! Thanks for the info.
Yes I have noticed the issue appears to be related on the specific scenario of Publisher on NET Framework version of the package.
Thanks