This is kind of a loaded question; running 20 instances of the same
executable for crash-proofing is like using 20 garbage trucks to pick up the
trash in your kitchen trash container. There are much more robust ways to
wire up a single service for crash-proofing, not limited to good exception
handling, Syslog messaging, and setting the recovery options in the Service
Manager to restart the service if it fails.
Having said that, the only requirement is that the ServiceName property in
the installer and the Windows service class must be different. And of course,
the actual executables must be located in separate folders.
Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"Geir Sanne" wrote:
hi!!!
i want to make 1 windows service and be able to run like 20 independent
instances of this.
the main reason i want this is to be able to see the names of the processes
running and to be able to restart the processes that has crashed.
is it a way to do this ?