I am looking to evaluate Aspose.Pdf as a possible printing solution for a client of ours.
One of the primary concerns we have is determining whether the printing of the document actually occurred or not. So this means if there was a paper jam, the printer was out of ink, etc., we would need to know. We will be charging clients’ money based on whether the print was successful or not, so it’s a big deal to ensure with 100% certainty that the document was printed.
Will Aspose.Pdf be able to do this? Basically we need confirmation of success even after the document is spooled to the printer.
Hi Andrew,
Thanks for contacting support.
I am afraid the requested feature is currently not supported. However for the sake of implementation, I have logged this requirement as PDFNEWNET-36460 in our issue tracking system. We will further look into the details of this requirement and will keep you posted on the status of correction. Please be patient and spare us little time. We are sorry for this inconvenience.
@AndrewDunaway
At the moment, Aspose.PDF uses the .NET GDI Print Path (provided by the System.Drawing.Printing API) that unfortunately doesn’t allow to check the print job status the way the you requires. In the future, we plan to add more ways to print document, including more modern .NET XPS Print Path (System.Printing API) that allows to check actual print job status. Still, it depends on the printer to report reliably its status back to the API used, so if the underlying Microsoft .NET API is unable to determine the job status due to the printer not reporting it back, Aspose.PDF will be unable to report it too.
We cannot at the moment provide the ETA for new printing paths, but they definitely won’t arrive before the late 2026, and maybe later. In the meantime, you may use the PdfViewer.CustomPrint event to implement the XPS Printing Path or custom printing mechanism with job status control themselves, or avoid using the PdfViewer at all and convert their documents to XPS to use the XPS Printing Path directly.