I’m working on an ASP.Net web application where we need to generate PDFs containing a body based on HTML input, plus headers, footers and watermarks. The way we’re currently making these with Aspose is using TextStamps.
The issue is, as soon as there’s a TextStamp in a Document, when our client tries to print the PDF file it makes the printer crash - printing queue blocked and printer basically out of order. It does so for all printers at our client’s site (they’re all the same brand but different models), which is kind of problematic. Our client would also like to share PDF’s with other organizations/individuals and we can’t afford these files to be “dysfunctional”.
A quick fix we found was to check “print as image” in Adobe Reader printing options and then it goes fine. Doing that at each print isn’t a satisfying solution in the long run though, especially considering we have lots of users and it’s difficult to make them all aware of that trick.
- Has anyone experienced these crashes with overlaid PDF’s ? Is this a known issue, if not with Aspose, with some printer drivers ?
- Is there any way Aspose can generate PDF’s in image format as this seems to be working when we check that option in Adobe Reader ? I did a little research on that but all I found was how to generate a real image (.jpg, .png) from a PDF document, not converting all of a document to image format and still keep it as a PDF.
Aspose.PDF dll shows 184.108.40.206 as a file version and 2012.12.09 as a product version. We use PdfConformance.PdfA1B. A simplified version of our code is in the file attachment.