> > > I should probably mention that this needs to work on both Unix and > > > Windows. > > > Our test on Windows shows that System.Drawing.Print does not work for > > > services. This is consistent with the MS documentation. > > > (btw: In my opinion, a system that requires access to a graphic > > > display in > > > order to print, is broken) > > Have you tried setting the "allow interaction with desktop" option > > for the Windows service? That should allow access to graphics; not > > sure about Microsoft's implementation of printing though. > No, I have not tried that. I resent doing that, actually. I simply can not > understand that one should have to allow something as lowlevel as a > print "thingy" to interact with the desktop. Clearly it can not be a sound > design?
Tomcat (Java) does much the same thing, it tries to access DISPLAY unless explictly told to run headless. You could just create PDFs with one of several assemblies for that purpose. In any recent LINUX/UNIX system you can submit a PDF directly to the print system and it will print. Don't know about Windows, but I'd bet you could rig it.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
