brettv
05-31-2005, 03:57 PM
Hi,
We need to customize our installer so that it installs certain files for some customers and not for others. Do you have a recommendation for the best way of doing this?
Ideally, we would love to have a single .ism file but build different setup.exe's, one for each customer (containing slightly different files). I haven't found a good way of doing this. Here are the ideas I've come up with so far:
1. Add all custom files to the .ism and use Install Conditions on reach component to choose which files to install. Ask the customer which customer they are during the install. Disadvatage: setup.exe contains files for other customers and requires extra interaction with the user
2. Have a seperate .ism for each customer. Disadvantage: hard to keep .ism's in sync when changes need to be made for all customers at once.
Is there a better way to do this? I.e. by configuring files per "Release" or by using a "Network Repository" with the shared elements or by using "InstallShield Assemblies" for the shared elements? Has anyone had success with implementing this sort of "per customer" scenario?
Thank you!
We need to customize our installer so that it installs certain files for some customers and not for others. Do you have a recommendation for the best way of doing this?
Ideally, we would love to have a single .ism file but build different setup.exe's, one for each customer (containing slightly different files). I haven't found a good way of doing this. Here are the ideas I've come up with so far:
1. Add all custom files to the .ism and use Install Conditions on reach component to choose which files to install. Ask the customer which customer they are during the install. Disadvatage: setup.exe contains files for other customers and requires extra interaction with the user
2. Have a seperate .ism for each customer. Disadvantage: hard to keep .ism's in sync when changes need to be made for all customers at once.
Is there a better way to do this? I.e. by configuring files per "Release" or by using a "Network Repository" with the shared elements or by using "InstallShield Assemblies" for the shared elements? Has anyone had success with implementing this sort of "per customer" scenario?
Thank you!