>> I didn't explain this well did I. Talker.exe is a GUI
>> application/service.
>> It has a main form included so that you can input connection details
>> and text to send to the other Talker.exe over a network. It also allows
>> you to preview the text before you send it to the remote Talker.exe -
>> Thus it has a UI.
>
> Nothing in that paragraph should be done in a service at all. You are
> interacting with the user. That is best done with a non-service
> application. The actual talking can be done in a service, where the
> non-service application transmits the text to the service via some form of
> inter-process communication. But the UI itself does not belong in a
> service
> at all. You can include the UI in the same .exe file if you wish, but
> like
> I said earlier the startup code would have to detect the mode in which the
> .exe is to be run. The same .exe could be running in a service mode in
> one
> process, and in a non-service mode in another process.
So basically, as long as I skip creating the form if the program is running
as a service I am ok?
I'm assuming then that (as you said) I can still include the forms in the
.exe but simply avoid creating them.
