I think you will need to be more specific about exactly *How* you're starting
this app from another machine. Does it use Remoting? Are you just logging
into a Terminal Services client to the remote desktop and then starting it
there and logging off? Without any specifics, it becomes a lot harder to
suggest alternatives. These could include having a remoting server that
clients could subscribe to or poll, sending messages via MSMQ, logging Syslog
messages to a listener, or a dozen other ways.
Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"Jason" wrote:
I've a c# app that I execute on a remote machine, which works as I expect it
to, but when I encounter an error on the remote machine how do I know what's
going on, since it's a remote app?
For instance on the remote app that I execute I check for the existence of a
file, and if it's not there,I want to display a simple popup message telling
the user that the file doesn't exist on that machine and then I quit the
app. How do I send a message, back to the user that started the remote app?
Any ideas, or examples?