Re: Same win service with different display names and description

 
Phil,

That was the initial design, but the client insisted to have 4 different
services (one per each interface) for reasons that are beyond the scope of
this forum. I had in mind the exact same arguments when I started designing
the application, but later I had to twist the design and accommodate
whatever they were asking me to do.

Thanks for your insight, nonetheless.

Regards,
Eddie


-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[email protected]] On Behalf Of Phil Sayers
Sent: Monday, November 24, 2008 1:23 PM
To: [email protected]
Subject: Re: [ADVANCED-DOTNET] Same win service with different display names
and description

Is it possible to shuffle your code around so that there is only 1 service,
and it manages "x" number of interfaces.

Using the servicename.exe.config file to define each individual interface?
Each interface definition in the .config could be a different thread working
with a different "interfacemanager" object (pseudo architect whiteboarding
in my head)

This gives you some flexibility in that you can support any number of
interfaces, you are not stuck with 4 and only 4.

It may mean a little more work in terms of adding more UI elements to allow
management of each interface.  Assuming you want 4 distinct services to be
able to start & stop each one independantly?

This would make your current deployment methodology a little easier, and (a
nice side effect) smooth the path to a full blown MSI installer if you ever
need it.
Installing the same set of binaries multiple times is not a fun MSI task,
all sorts of headaches related to GUIDS that can be much better explained by
"a different Phil".





-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[email protected]]On Behalf Of Eddie Lascu
Sent: Monday, November 24, 2008 10:17 AM
To: [email protected]
Subject: [ADVANCED-DOTNET] Same win service with different display names and
description


Hi there,

I have one windows service that I need to deploy 4 times on a production
server. Each service will control a different interface. The interfaces are
100% similar so that is why it made sense to develop only one service. Now,
that I need to deploy them, I also need to instantiate them with different
display names and descriptions. The display name and the description are
properties of the serviceInstaller object. Is there a way to change those
two properties other than changing them in my development environment and
then recompile the whole service? Is there some kind of configuration file
for the service itself where these properties would be stored and then read
by the service during the installation phase?

Thanks for your help,
Eddie

===================================
View archives and manage your subscription(s) at
http://peach.ease.lsoft.com/archives

===================================
View archives and manage your subscription(s) at
http://peach.ease.lsoft.com/archives

===================================
View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives