configuring a service that is in a merge module
interesting question here chaps.
We have a bunch of in-house exe's that need to get placed in a MSM as different in-house packages use these exe's.
Some of the exe's are configured as services by these packages and I am wondering if i can create a configurable merge module which will fit our needs.
For example: -
pkgA consumes the MSM and configures test.exe to run as a service called serviceA.
pkgB consumes the MSM and configures test.exe to run as a service called serviceB.
pkgA gets installed and then pkgB go down on the same machine, will this cause any issues?
Does anyone have a better solution?
We have a bunch of in-house exe's that need to get placed in a MSM as different in-house packages use these exe's.
Some of the exe's are configured as services by these packages and I am wondering if i can create a configurable merge module which will fit our needs.
For example: -
pkgA consumes the MSM and configures test.exe to run as a service called serviceA.
pkgB consumes the MSM and configures test.exe to run as a service called serviceB.
pkgA gets installed and then pkgB go down on the same machine, will this cause any issues?
Does anyone have a better solution?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
I don't know what you mean by 'pkgA "consumes" the MSM'.
Also, when you say 'pkgA [snip] configures test.exe to run as a service', does that mean that test.exe can run as a console app instead?
Or, is it simply that you want test.exe in an MSM which pkgA and pkgB will need to include?
If the latter, I can't see a problem. MSMs are essentially libraries in MSI form, ready for inclusion in other MSIs in order that the content of those MSIs is standardised (i.e. as far as what the MSM contains, of course). They're no different really to DLLs in that sense.
Also, when you say 'pkgA [snip] configures test.exe to run as a service', does that mean that test.exe can run as a console app instead?
Or, is it simply that you want test.exe in an MSM which pkgA and pkgB will need to include?
If the latter, I can't see a problem. MSMs are essentially libraries in MSI form, ready for inclusion in other MSIs in order that the content of those MSIs is standardised (i.e. as far as what the MSM contains, of course). They're no different really to DLLs in that sense.
Posted by:
frodo
16 years ago
hi thx for the repsonse, your right there, i mean that pkg A and pkg B both include the merge module. the issue i am thinking about is that the merge module contains the exe's but pkg A and B will configure these exe's differently to run as particular services with diff service names.
if i install pkg A and pkg B (no upgrades\no relation) will the service get configured without changing the already installed service?
if i install pkg A and pkg B (no upgrades\no relation) will the service get configured without changing the already installed service?
Posted by:
jmcfadyen
16 years ago
your probably better writing some code to inject it if its a common item
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.