I'm afraid this is not a good solution in this case. You will need to create a separate aip file for each customer an then customize them using the command line tool.
I've been doing this for over 2 years with AI, very successfully. Note that I had mentioned we use the /DuplicateProject command-line option for each of our customers before modification. This is the point of the template feature. I've discussed this in detail with other members of support.
Keeping separate aip files for each customer is dangerous, because if you make a change in one, you need to make the same change in all of them. OK for 2 or 3 customers, but if you have 50 or 100, something will be missed. Thus templates... Change the product name, version, phone number, and any other properties that are used by CAs and other parts of the installer.
I have done this in the past with InstallShield, and for companies that OEM/brand their software, such as ours, it is a best practice.
Please note that the prerequisite name is pseudo-formatted, this means that the value of that property will be resolved at build-time, not runtime.
Yes. Exactly what I want.
Also you should now that Windows Installer public properties cannot be accessed or modified by an EXE file. You can modify or read the value of a property using a C++ DLL or VBScript.
Since our bootstrapper is an EXE file you can understand that properties cannot be used by it.
Yes, I am very familiar with the restrictions, which is why we use build-time branding, not runtime branding.
I'd like to repeat my request that your product team consider adding the ability to use properties in prerequisite conditions (which are resolved at build time).
FOLLOW US
Get the latest news in Application Packaging