The issues you have found earlier (filed as PDFNET-48232,PDFNET-48386) have been fixed in Aspose.PDF for .NET 20.7.
Issue still not fixed with 20.7 and 20.8 version. Please check below shared code. It’s been hard to answer our client now. Please take this as priority.
We tested the scenario using following code snippet with Aspose.PDF for .NET 20.8 and were unable to notice any issue.
Document doc = new Document(); Document mDoc = new Document(dataDir + "MM_20200325_Stations Interdiciplinary Minutes.pdf"); doc.Pages.Add(mDoc.Pages); doc.Save(dataDir + "merged20.8.pdf");
merged20.8.pdf (8.2 MB)
Could you please share a bit more details about the issue that you are facing at your side. Also, please make sure to use a valid license while merging the PDFs.
The solution you have suggested is not working for us so can you please suggest another solution We are still facing issue.
As requested earlier, would you kindly share some details about the issue that you are facing? Is it slow performance of the API? OR you are facing some issue in resultant PDF document?
I see your suggested code differs from the one we have. But at this moment, it’s very tightly coupled in our enterprise level application and it’s very risky to do that for us. Please provide us another solution.
In your shared application, you are using FileStream to read and write the files. We tested using FileStreams as well. Also, we tested the scenario using your shared application with Aspose.PDF for .NET (20.8 and 20.9). We did not notice any issues. We request you to please share some screenshots of the issue that you are facing so that we can also try to replicate it in our environment and address it accordingly.
MergeResult_090520034655.pdf (8.2 MB)
As you said in a previous comment here I am sending you video of our issue using 20.8 & 20.9 so please check it.
Thanks for sharing the videos and explaining the issue to us.
The exception which you are facing is due to trial version limitation. Would you kindly make sure that you are setting the license correctly before using the API. OR please check if you are using a valid license with v20.8 or v20.9. In case issue still persists, please share your license file with us in a private message. We will test it in our environment share the feedback with you.
You can send a private message by clicking over the username and pressing Blue Message Button. We strongly suggest that you do not share your license publicly.
Thanks It is working.