Our system automates printing to a custom printer using ShellExecute and the PrintTo verb.
I know that for some version of Acrobat Reader, the /t flag used to open a file, print it to a specified printer, and close it - and from some version of Adobe Reader, this behavior changed so that the document prints but Acrobat doesn't close.
Although I don't see the point of keeping Acrobat open, that in itself is not such a huge problem.
However, in Acrobat Reader DC, we have encountered a new problem: After we print a document using PrintTo, Acrobat Reader stays open, and does not respond to printing requests anymore.
Our intermediate solution was to change the command saved under the PrintTo verb, and add the /n flag. This opens up a new instance of Acrobat Reader every time we call PrintTo, but for some reason, this actually behaves as I would expect it, and closes the new instance after printing.
The first instance will always stay open.
Is there a better solution to this, perhaps something at the software configuration level?
Is this a bug in Acrobat Reader DC, that prevents the program from responding to command line printing (perhaps responding to command line commands at all) when the opening screen is displayed?