We are using Advanced Installer and we have a question regarding using a single aip project with multiple builds to produce different setup files for our OEM partners.
I am using a single aip project and I have created different Builds in the Deployments --> Media. I have also created Properties in the Product Information --> Install Parameters which have different values depending on the Build.
While this achieved most of what I need, there are places where I cannot utilize these Properties and I am forced to use a hardcoded value for all the different Builds. Here are three examples:
1) In the Resources --> Files and Folders, when I open the Application Folder Properties dialog and select the Synchronize Tab, the Source Folder cannot be based on one of the Properties defined, but rather it must be a hardcoded path. I don’t want to create an OEM specific folder for each OEM we have and keep changing that every time we add a new OEM
2) In the User Interface --> Dialogs, the LicenseAgreementDlg AgreementText RTF File, the name of the text agreement file must be a hardcoded file name and not based on one of the defined Properties which changes its value from one build to another. How can we have a different License agreement file for each build that we support?
3) In the Custom Behavior --> Custom Action, I am running a VB script to create the shortcuts. Can I have the name of the VB script to be based on a Property value?
Can you please inform me whether we can use the Properties in the three stated areas or not. If it is not possible, can you please suggest how to produce different setup programs from the same aip project to be used by our OEM partners.
Many thanks.
FOLLOW US
Get the latest news in Application Packaging