Hi!
ilyaz wrote:
When testing I launch the utility from the command line several times in a row processing a bunch of PDF files one file at a time.
The source code of PdfFilePrinter is included.
It was developed for Adobe Reader 7 and contains a hack: if no instance of Adobe Reader is running, it starts a new one.
So if you create several PdfFilePrinters in a very short time, more than one of them may find there's no Adobe Reader running - and more than one gets started (one loading invisible, others loading with a Window).
If that is the problem, then you'd better have one process that does all the printing - and the command line utility only adds print jobs to the queue of this service.
PdfFilePrinter is just a helper that calls Adobe Reader with some command-line parameters. You can vary the code and/or the command-line parameters to see if that makes a difference.