The problem:
Our licensing agreement is often created after our release build is built. This means we have to rebuild our installer after we receive the new license agreement. It would be nice if we didn’t have to rebuild the installer just for the new license agreement.
I’m wondering if one of the two solutions is possible in Advanced Installer/MSIs:
- Set the license file to be loaded dynamically from the location of the bootstrapper/MSI. I.e., specify the path as SourceDir\Eula.rtf. This way, when we receive the new Eula.rtf, we can just drop it into the installation folder (next to the MSI file).
- Make the Eula.rtf file a binary file in the built MSI (make it show up in the “Binary” table of the MSI). I believe this would allow the MSI to be updated with a new EULA via Orca?
Thanks.