One of the most straightforward methods that I can think of would be to use
remoting. Remoting lets you appear to instance an object in your client
code that is really running in the server process (kind of like DCOM).
A pro would be that you would actually be able to install the admin tool on
separate workstations if you wanted to. One con that I can think of off the
top of my head: using the built-in remoting channels, the server would be
required to have TCP/IP, even if both the service and the admin tool were
running on the same box -- that's because the remoting channels that come
with the framework route their messages through TCP/IP.
"Adam Clauss" <ca*****@tamu.edu> wrote in message
news:u1***************@TK2MSFTNGP11.phx.gbl...
I am currently developing an application which will primarily run as a
service that starts with Windows. However, I want to also have an 'administration' tool that can be run that controls various
aspects of the service (not simply start/stop). What methods exist to communicate between these two separate processes? And pros/cons
of them?
Thanks!
--
Adam Clauss
ca*****@tamu.edu