I have a handful of different web installer build configurations that I would like to each have modify an XML file. Each should update the same XML file and the same node value, but setting it to a different value.
Aside from this single XML edit, these builds are all identical. Since the application is fairly large, each build configuration is set to download the same .msi file to use during installation.
I have set up a custom install parameter and have overridden the value of the parameter to be specific to each build configuation. For editing the XML file, I have set up my installer project to use the value of that parameter when updating the XML. The problem is, it seems that value gets hard-coded into the msi file. The result of this is that the last build configuration to be run sets the XML value to what it needs, but then all of the web installers end up with that same value being inserted into the XML since they all install from the same msi file.
How can I make updates to an XML file using values associated with the web installer's bootstrapper exe instead of having it hard-coded into the underlying msi?
FOLLOW US
Get the latest news in Application Packaging