You ^could^ have them as one application, but it is NOT advised. The
reason for this is that a service runs all the time, and you don't always
have an interactive user logged in with a desktop to interact with. Or, you
might have multiple interactive users logged into the service.
If you have functionality that is shared between the programs, then I
suggest that you move that functionality into a separate dll, and register
it in the GAC. Then, have the service and the configuration window as
separate programs, using Windows Communications Foundation to make calls
from the configuration program to the service.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"SeeSharp Bint" <Se******@nospam.comwrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
>I have written a Windows Service application that does some scheduled small
tasks on one or more sql server databases.
I've written it so that it can service several databases. I've also
written a small application with a single main configuration window that
allows add/delete of databases, login details etc to a stored file
At the moment both of these are separate applications but I'd really like
to combine the two together as they're so closely related.
Am I able to do this please? If so then how? (ie I need to run it as a
service but somehow get to the configuration screen easily)
thanks :)
