Hi,
We have a family of products which have the same core components and executables, but different support files. These support files are additive - i.e. if I install product X and product Y I should get the core plus the files specific to X and to Y (with the core being upgraded as necessary if it has moved on between the two installations).
On uninstallation of X I should be left with core + Y (and vice versa).
So two questions:
- is this possible?
- if so, how do I go about it?
Thanks,
Ian
Multiple related installations
-
- Posts: 18
- Joined: Thu Mar 01, 2007 10:22 am
- Location: Edinburgh, UK
-
- Posts: 18
- Joined: Thu Mar 01, 2007 10:22 am
- Location: Edinburgh, UK
Here's what I'm doing
Hi,
Okay, here's what I've come up with.
Our products each have a unique ID which can be expressed as a 6-digit hex number.
I have set up the product GUID as
{77271EBD-#ID_PART1#-#ID_PART2#8E-AF2C-A4088D485549} (I took a generated GUID and picked on 6 digits in the middle).
I pass in ID_PART1=xxxx ID_PART2=xx when I build the kit from the command line (for example ID_PART1=1C23 ID_PART2=1F).
This generates a unique kit for each product.
I have marked the core stuff as shared.
This all seems to work.
Is there any reason I might see problems with this approach?
Thanks,
Ian
Okay, here's what I've come up with.
Our products each have a unique ID which can be expressed as a 6-digit hex number.
I have set up the product GUID as
{77271EBD-#ID_PART1#-#ID_PART2#8E-AF2C-A4088D485549} (I took a generated GUID and picked on 6 digits in the middle).
I pass in ID_PART1=xxxx ID_PART2=xx when I build the kit from the command line (for example ID_PART1=1C23 ID_PART2=1F).
This generates a unique kit for each product.
I have marked the core stuff as shared.
This all seems to work.
Is there any reason I might see problems with this approach?
Thanks,
Ian
Who is online
Users browsing this forum: No registered users and 166 guests