Recently, we upgraded from Aspose.Note 24.11 to Aspose.Note 25.6 and noticed that our solution stopped copying the Aspose.Pdf 22.8 DLL to the output directory.
After investigating, we discovered that the cause is an internal change within Aspose.Note—it previously referenced Aspose.Pdf 22.8, but now references Aspose.Pdf 24.3.
We have the following questions:
Why is the Aspose.Pdf DLL referenced by Aspose.Note?
When was the referenced version being usually changed, and why was it updated to 24.3 instead of the latest available version?
We will look into your issue. But could you kindly provide a standalone sample VS.NET project (zipped before attaching) to demonstrate the issue? This will help us evaluate your issue more accurately and work towards figuring it out soon.
But could you kindly provide a standalone sample VS.NET project (zipped before attaching) to demonstrate the issue? This will help us evaluate your issue more accurately and work towards figuring it out soon.
It’s mostly a question, rather than an issue. We faced issues in our project, but it’s not very easy to create a sample small project with similar symptoms. We fixed the issue by upgrading our Aspose.Pdf reference to version 24.3.
Here is a screenshot that showcases the difference between Aspose.Pdf versions referenced by Aspose.Note 24.11 and Aspose.Note 25.6.
Generally, Aspose.Note and Aspose.PDF are separate products, each designed to handle different document formats. Aspose.Note for .NET supports converting OneNote to PDF documents without using any other component. Apparently, Aspose.Note does not use Aspose.PDF internally. Anyways, I will discuss this matter in detail with the product lead soon and will provide you with further information. Thank you for your patience.
I discussed it with the product lead. Indeed, Aspose.Note has referenced (and still references) Aspose.PDF. This is required to support certain functionality, particularly importing PDF into a OneNote file (Import PDF to OneNote | Aspose.Note Documentation).
An issue occurred with version 22.8, caused by a bug in Aspose.PDF, which made it necessary to update the referenced version.
Currently, Aspose.Note targets .NET Framework 4.0 and .NET Standard 2.0, and version Aspose.PDF 24.3 is the last one that supports .NET Framework 4.0. Starting from Aspose.PDF 24.4, that target is no longer supported.
This update to Aspose.PDF 24.3 starts from Aspose.Note 25.6, in earlier versions, everything remains the same.
Hope, it clarifies everything.
Please let us know if you have encountered any issues or unexpected behavior due to this update?