if your first service blows up due to an unhandled exception, its going to
take your second "service" with it, because the process is going to go away.
Suggest looking into a more robust alternative for whatever it is you want to
accomplish.
Peter

Signature
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
> Hello,
> I've written a Windows service and i need help to implement the meaning
[quoted text clipped - 15 lines]
>
> 10x.
Hello, hagaihe@gmail.com!
[skipped]
h> My target is basically to implement survivability of my project so if
h> the service will "fall down" another process / user will be able to
h> continue.
h> Does someone have any idea ??
You can start several windows services with different names, if one fails another starts operaing
instaed of "dead" one.
--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com
Alan Pretre - 22 Aug 2006 16:03 GMT
> You can start several windows services with different names, if one fails
> another starts operaing
> instaed of "dead" one.
You can also set the Recovery option for a service to have Windows restart
it automatically if it dies.
-- Alan
Willy Denoyette [MVP] - 24 Aug 2006 00:11 GMT
Please don't push people to start 'shadow' service processes, keep in mind
that services use precious resources not consumed by regular processes.
Better is to look at the option presented by Alan, unfortunately it's not
that easy to achieve from within .NET. Also, services should be as robust as
possible, but <rant>.NET has changed this picture, seems like everyone needs
to write a bunch of services these day's :-). Most of the time they crash or
hang or exhaust precious system resources, but no trouble start another one
when the first fails....</rant>
Willy.
| Hello, hagaihe@gmail.com!
|
[quoted text clipped - 12 lines]
| Regards, Vadym Stetsyak
| www: http://vadmyst.blogspot.com