Problem in .net core 3.0


For a project that we are working in the preview version of .net core 3.0 , we’ve stumbled on problem.

When we open a pdf file in the Aspose.Pdf.Document class, do no changes, and saving the document into a new pdf file, the new pdf is blanco or corrupt in acrobat reader Version (19.012.20034).

The aspose.pdf version we are using is 19.5.0

When we switch to the .net core 2.2 version it the new generated pdf file seems ok.

Can you you give us an update when will you support .net core version 3?

See the zip for a sample. (331.6 KB)

Thanks for contacting support.

Yes, API has support upto .NET 2.0 and a feature request for .NET Core 3.0 support has been logged in our issue tracking system as PDFNET-46423. We have linked ticket ID with your post and will let you know as soon as required support is available. Please be patient and spare us little time.

We are sorry for the inconvenience.


we are experiencing the same issue as described by
Can you provide us with an approx. estimation when the update to Apose PDF will be released? (I can’t take a look at the linked ticket due to the lack of paid support)

The issue solely occurs when using Adobe Acrobat to open the generated PDF files. Other PDF viewers and browsers like Chrome or Firefox don’t seem to be affected by this.


The issue logged for this thread is related to support of .NET Core 3.0 because API was unable to generate correct PDF file in this version of .NET Core. Would you please confirm if you are also working in this framework and facing similar issue. Otherwise, please share a sample code snippet along with sample PDF document. We will test the scenario in our environment and address it accordingly.

Yes, as I’ve said, we are experiencing the exact same problem as
using .Net Core 3.0 Preview in conjunction with Aspose PDF 19.6.0 results in blank/empty PDF files when viewed with Adobe Acrobat.


Thanks for confirming the issue.

We have recorded your concerns along with the logged issue.

Please note that the issue is logged in free support model and will be resolved on first come first serve basis. However, we will surely let you know as soon as issue is resolved. Please spare us little time.

We are sorry for the inconvenience.

Also interested in this, as we are currently targeting .net core 3 now it’s been officially released.


We would like to share with you that implementation of requested feature is currently is in progress. We are working over its implementation and as soon as work is complete, we will surely inform you within this forum thread. Please spare us some time.

We are sorry for the inconvenience and delay.

@asad.ali I am not getting this issue in 19.10 in .net core 3, but this is not in your release note. Is this something that is officially fixed, or something which is still in progress and only partially fixed


Thanks for noticing the missing ticket in release notes and notifying us about it.

We have now updated the release notes page and would like to share with you that .NET Core 3.0 support has been added in the API and available in latest version.