Hi,
I have a service which is only a server for some objects the user can
instanciate and call.

Right now, the service starts and then stops automaticaly. The only line of
code I added is in the OnStart event and is
"RemotingConfiguration.Configure(configfile)". So I guess the service is
stopping because it has nothing better to do?

Is there a setting I can set to prevent it from stopping? will I have to
start a loop that will run until the OnStop event runs in order to keep the
service alive?

Thanks

ThunderMusic

Did you try changing the service startup type to "Manual". ?

Thanks.
Ramu



"ThunderMusic" <NOdanlatSPAM@hotmaildotcom> wrote

no, I want it to be automatic... I just want it to stay alive after it
starts...


"Ramu Nallamothu" <rnallam (AT) hotmail (DOT) com> wrote

ThunderMusic wrote:

Perhaps if you gave it something to do? A timing loop, something like that.
--
Gregory Gadow

Hi,

No.
If you are using the default generated code for the service this should
include a call to System.ServiceProcess.ServiceBase.Run in its Main. This
keeps the service running until it is explicitly stopped.

The usual reason for a service mysteriously stopping is an exception (which
doesn't show because services don't have a UI by default).

Cheers
Doug Forster

"ThunderMusic" <NOdanlatSPAM@hotmaildotcom> wrote

OnStart is an "event" that gets called when your Service is initiated, to do
initialization etc. You would typically start a thread there (ThreadStart
for some method you run) that runs until some event happens, you trigger
that event in OnStop().
--
Phil Wilson [MVP Windows Installer]
----
"ThunderMusic" <NOdanlatSPAM@hotmaildotcom> wrote

ThunderMusic wrote:
while run_flag
system.threading.thread.sleep(150)
end while
).
Onstart is only the initializer, not the worker - i.e. if you loop in onstart, you will get an error that the service did not respond in a timely fashion...

on onstop method set the run_flag to false and release resources.