J
John
I currently have a Windows Service that runs Transactions that are very
Processor/Memory Intensive. I have a requirement to deploy multiple
instances of the Web service on the Same server. Each Instance needs to
run in its own process.
My current approach to this is to put all the logic into a separate
"Worker" assembly and install it into the GAC. I'm then going to create
Multiple Windows Services (i.e. MyService1, MyService2 etc..) that each
instantiate "Worker" . I will then have a separate install program for
each Windows Service. (Not exactly elegant)
Any suggestions on this approach?
Is there any Way to have one "codebase" for the Windows Services rather
than having a project for "MyService1", "MYService2" etc..?
Does having the "Worker" assembly in the GAC affect performance at all?
Is there an easy way to install Multiple versions of the same Windows
Service on the Same server (I can't seem to find one)
Thanks in advance !!!
Processor/Memory Intensive. I have a requirement to deploy multiple
instances of the Web service on the Same server. Each Instance needs to
run in its own process.
My current approach to this is to put all the logic into a separate
"Worker" assembly and install it into the GAC. I'm then going to create
Multiple Windows Services (i.e. MyService1, MyService2 etc..) that each
instantiate "Worker" . I will then have a separate install program for
each Windows Service. (Not exactly elegant)
Any suggestions on this approach?
Is there any Way to have one "codebase" for the Windows Services rather
than having a project for "MyService1", "MYService2" etc..?
Does having the "Worker" assembly in the GAC affect performance at all?
Is there an easy way to install Multiple versions of the same Windows
Service on the Same server (I can't seem to find one)
Thanks in advance !!!