Indeed, the chained MSI cannot be added to repository. The encountered behaviour is correct. We didn't find necessary to add a chained .MSI to repository since there are not many settings to be saved.
The prerequisite repository is useful for packages where a lot of settings are necessary (e.g. install conditions, UI command lines, etc).
I want to chain to a MSI file that is outside of the main project so the path on my PC may be different from our build server's path.
Having the MSI in the AI repository meant I could have my local repository defined on a different path to the build server repository path and both would be able to retrieve the file.
As the repository is not supported for chained prerequisites I though of using a property in the path but that is not supported. I then thought of converting the project paths to use variables but the path to chained msi files is not listed by the wizard.
I am now stumped as to how my local builds and builds on the build server can retrieve the same external MSI file where the paths are different.
On further investigation I see that the prerequisites repository is not what I thought it was. It stores an aip file describing the prerequisite but not the msi file itself.
What I'm after is a relocatable store of the chained MSI files so I can build the same installer on 2 PCs with different folder paths.
FOLLOW US
Get the latest news in Application Packaging