To Window Service..Or not to window service?

[TCarter]

Howdy fellas,

Just looking for some insight.


I am making a server program, it works, cool.

Made it display the info coming in via a textbox, the number of users connected, etc.


I based it off of one of the members heres examples (jmcilhinney).


However, I am kind of in a rock and a hard place.

Do I try and convert it to a windows service so its on all the time? Or do I leave it in a exe format?


I have never touched windows services before, but they look promising.

Q. Do windows services reboot the service if the service were to crash?


----

I wouldnt mind leaving it as a normal exe, and just leave it running, as I like looking at all the stats and such.

However, this will be residing on a collocated server running Windows Server 2003.

The problem with that is, if I run it. Person B, C, D, E, whoever.. can not see it due to the virtualized desk tops of RDC (even under the same username).


I am kinda curious if I should make it a windows service, then make my 'display' program that just.. remotely taps into it to control it, and view stats and such.


The 'server' will take info sent from the client, and add it into a database, then pass back some commands and such.

Just, curious what you guys think. Thanks.

[sapator]

Personally in this situation i would have left it as it is.
If you where to convert to a service then you need some basic knowledge and you must also use threading to have the service interact with the desktop so you can see the stats,etc.Also as you said i don't know how it reacts with RDC.
Also services are harder to debug.Especially if you expect form control reactions.
I usually make an exe app, debug it and then pass it on a service and then debug it again...And again.Have a look here http://msdn.microsoft.com/en-us/libr...=VS.80%29.aspx
Also here.
http://msdn.microsoft.com/en-us/libr...8VS.80%29.aspx