All true, but since the OP indicated that the application hosts a web
browser control (the WebBrowser control that I assume), I would assume that
there is ^some^ degree of control of the client execution environment (or
more specifically, that there is an install of some sort where the driver
can be installed, it doesn't have to be set as the default).
Also, since it is a .NET app, this wouldn't be the only cross-platform
concern if the app were ported.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Michael B. Trausch" <mi**@trausch.uswrote in message
news:20081111164705.6c7b44ce@zest...
On Tue, 11 Nov 2008 16:36:14 -0500
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com>
wrote:
>>
There is also the option of creating a print driver of some sort
which will basically act as a virtual printer (something like the PDF
print option that Adobe offers).
This assumes total control of the client execution environment, whether
or not the user is doing this is undetectable from the Web application
itself. Also, since it'd be a global setting, may cause far more
trouble than solving the original problem... and, of course, such a
solution is system-dependent. You lose portability if you depend on
being able to deploy something like this across clients, since print
configuration is not inherently cross-platform.
--- Mike
--
My sigfile ran away and is on hiatus.
http://www.trausch.us/