I wish it were that simple. Everything is running locally on my workstation
at this stage.
I agree that if no errors are thrown the call may be working, but why is
nothing coming out of the printer? More likely, I think, is that the call is
being blocked when running under the ASPNET identity used by the Web Service
(or some other webservice related limitation). I would expect this to throw
a security exception, and it doesn't. Hence my post.
Regards,
Peter
"Alvin Bruney [MVP]" wrote:
no errors are returned because most likely, the call succeeded. you realize
that you are tring to print on the server and not on the client right? which
is why the windows forms version will succeed and the webversion will not.
--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok
"Peter Wood" <Pe*******@discussions.microsoft.com> wrote in message
news:72**********************************@microsof t.com...I am attempting to run an external process from within my web service, but
nothing happens. No errors are thrown, nor are any eventlog messages
written. If I call the same classes directly from a WinForms app (not
through the web service), it works fine. I realise that the difference is
that the webservice runs under the ASPNET user and WinForms is running
under
the interactive user (I have checked, and this is the case). Both are
local
admins. Because there are no errors, I don't know where to go next.
Can anyone help?
This is the call:
System.Diagnostics.Process process =
System.Diagnostics.Process.Start(printAppPath, args);
Thanks,
Peter