I am just trying to understand some design concepts before I continue any further.
I have been working on a control panel program that also starts a com server exe.
The com server performs the heavy lifting.
I need the program to start up when Windows Server starts, so I was going to use Task scheduler to start the program.
However, from what I gather, only programs configured to run as a services will start up when the Windows Server is started/rebooted.
A standard program will require someone to log into one of the accounts before being able to be run.
Therefore I need the com server part of the program to run as a service on startup and the UI can be run on an as needed basis if required.
So the questions are:
Should I revert the com server exe back to a regular exe?
If I start the com server (Or regualar exe) first as a service, how do I communicate with it later from the UI?
At the moment I create an object reference to the com server when it starts and hold that in a _Screen property.
I know I got a lot to do, but a help being steered in the right direction would be greatly appreciated