Hello Ed,
It is considered best practice that a Windows Service does not display a
User Interface, and I would recommend sticking to that recommendation
for a multitude of reasons. Services should be able to perform their
tasks in an unattended mode.
This does not mean that you could not write a user interface
application, which interacts with your service through some means of
inter-process communication, for example through remoting, Web Services
or Sockets.
This way you get the best of both worlds: Unattended execution of your
background processing, and interactivity through a GUI.
Bennie Haelen
Ed wrote:
Is there a way to run an application in the background other than through a
service.
As I understand it when creating a service it is best practice not have any
kind of user interface. My application doesn't need an interface all the
time, but it does need it periodically. This is why a want to do something
other than a service.
Can I inherit a class from a System.Diagnostics.Process class? If so, how
do I make the Main() function to start it?
thanks in advance,
ed