A single aip project with multiple Builds - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

amir
Posts: 1
Joined: Tue Mar 06, 2012 2:12 am

A single aip project with multiple Builds

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.
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: A single aip project with multiple Builds

Hi Amir,

Here is a copy of my e-mail reply.

1) For this you can use our Path Variables support, but you will need to build the project from command line, separately for each user. Our command line allows you to change the value of a per-project defined path variable so you can change it for each build to different source.
http://www.advancedinstaller.com/user-g ... ables.html

After you set the default path for the synchronized folders, you can right click on one of them and select "Convert File Source Paths..." so the project will use your new path variable.

2) In this case path variables unfortunately cannot be used so there is a single solution, which is not very elegant unfortunately. You will need to manually create multiple new dialogs, license agreement dialogs, by copying the controls from the predefined one and updating the control conditions.

Than, on each dialog you need to right click and use the option "Show only if", setting the condition based on the build name, like this:

Code: Select all

AI_BUILD_NAME="DefaultBuild" 
3) Unfortunately this is not possible, but you can have multiple custom actions, which use as execution condition the name of the build, the same way you would do for the custom dialogs.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”