We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Printing Performance with Split Documents


I am printing off a batch of letters with Aspose.Words. The letters are Duplex and want to be printed on Headed Paper but specifically I want to print on the front AND BACK of the headed paper. I’m printing 400 different document formats so changing the documents isn’t an option.

So what I am doing is:
For each Section in the document set the PageSetup.FirstPage and OtherPages to Tray 1 (where the Headed Paper is) then printing page 1 & 2, then setting the PageSetup.FirstPage and OtherPages to Tray 2 (where the Continuation Paper is) and printing the rest of the document.

This works well, but it is slow.
So I thought Id multithread it, which improved the performance brilliantly. But when multithreading the printing I cant guarantee the order of the documents, so Page1&2 of Document 2 is likely to come out before the other pages of Document 1.

Can you think of any way around this. can I print pages 1&2 to a file and then add the other pages or something like that.
Can I use some sort of clever PostScript rendering?
If I synclock the threads then it defeats the object of multithreading. Would UpdatePageLayout multithreaded make a significant difference? If I change the paper source will this rendering model need updating anyway?

Its an interesting problem. Have you got any ideas?


We are checking this scenario and will get back to you soon.

What about using AsposeWordsPrintDocument.Print to produce the document. This might give me more control over individual pages, but is this safe in a multithreaded environment? And can I disable the Print Progress Dialogue.

I remember how to disable the Print Progress Dialog. Changing the default AsposeWordsPrintDocument.PrintController to a new System.Drawing.Printing.StandardPrintController.

What about multithreading and: AsposeWordsPrintDocument.Print()


Yes, it supports multithreading.

Also, the idea to use multithreading for building layout sounds really good. The UpdatePageLayout method is called upon printing. So, you have to do multithreading on UpdatePageLayout method with applied settings (the layout model will be created) and then run your printing job in one thread.

Please try these options and let us know how it goes on your end?

Ok, it looks to me like using Aspose.Words.Rendering.AsposeWordsPrintDocument and printing page by page will give me control of the PaperSource perfectly.
Is there a similar pattern I can use for PDFs? I can see there used to be a PrintController in the Aspose.Pdf.Generator namespace but that isn’t there anymore.


We are afraid that, currently you may not control PaperSource while printing a PDF document. However, we have logged an investigation ticket with ID PDFNET-45277 in our issue management system for further investigations. The ticket ID has been linked with this thread so that you will receive notification as soon as the ticket is resolved.

We are sorry for the inconvenience.

Actually: You have a PdfQueryPageSettings event on the Aspose.Pdf.Facades.PdfViewer that you can override to set the PaperSource in a very similar pattern. I’ve tested this and it works perfectly.


Thank you for your kind feedback.

We are glad to know that things have started working in your environment. You have managed to make it work using Facades approach. We will investigate under the logged issue if same requirements can be achieved using Document Object Model (DOM) approach. We will let you know if we have any further updates regarding this issue.

Please keep using our API and in event of any further query, please feel free to ask.