very newbie to InstallShield so please bear with me.
I have managed to produce an installer which deploys the required Win32 app/file, set up the registry based on user input (default folder locations and the like), and create a new, or upgrade an existing, SQL catalogue.
Different clients of ours require differnent files installed. I was hoping to hve an XML configuration file along the lines of...
file1.txt file2.txt
file1.txt file2.txt
etc....
then in InstallScript MSI simply set one property, the client name, in this case to abc or def then read in and set InstallScript variables to the rest of the configurations held in the XML document.
In the above example a LIST type variable containing the files needed for the specific client.
Is this doable without having to COM out to VB or C# and modify the ISM? Can I place an XML file in the Support Files / Billboards which can be read at runtime?
(As a side note following up on my post on the other thread, note that InstallShield collaboration underwent significant revisions between IS2011 and IS2012, so as of IS2011 I would lean towards automation as the better solution here.)
