Mitch
Posts: 10
Joined: Thu Mar 06, 2008 11:35 pm
Location: Golden, CO USA
Contact: Website

Organization Questions

I'm using AI Pro on XP and have some questions on the best way to organize an installation. The basic layout is

Program Files
Company Name
Help
Main Application
Helper Application

The Helper Application will also have a separate installation but we'd still want it to install with the same structure. So on the Install Parameters page I set the Application Folder to: [ProgramFilesFolder][Manufacturer].

This works but when I was testing the Helper App's Installation I did an uninstall and it removed the entire Company Name folder which also included a number of older applications which weren't installed with AI.

Is this an organization problem or a setting problem?

Would I be better off to create separate installations for the Help, Main and Helper App's and then combine them in a single installation?

Thank you,
Mitch
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,

Please note that all the resources registered into a MSI package will be removed when the package is uninstalled. This means that if you install the Help and the Application with one package, then if you uninstall the package everything is removed.

If you want to separate them, there are two solutions:
1) You use two different features for the Help and the application. This way, the user can launch the MSI package into maintenance mode (modify, repair and remove options) by using the "Change" button in "Add/Remove Programs".

When the user selects the "Modify" option, he can change which features are installed and which are not.

2) You use two different packages for the Help and the application. In this case, the best approach is this:
- create the MSI package for the Help (for example it is called "help.msi")
- add it to the "Files and Folders" page in the project of the application installation package
- go to the "Custom Actions" page and create a "Launch file or open URL" custom action under the "UI Custom Actions" sequence
- set the "Command Line" field to the help MSI file (for example: "[#help.msi]" - with the quotes)
- set the "Asynchronous execution, do not wait for return" option in the "Custom Actions" page
- go to the "ExitDialog" in the "Dialogs" page
- create a checkbox control which has the text: "Install Help"
- set the "Property Name" field of the checkbox to CHECK
- create a "DoAction" Published control event for your custom action which looks like this:

Code: Select all

DoAction     viewer.exe      CHECK
where "viewer.exe" is your custom action. This will launch the installation of the Help files if the user checks the "Install Help" checkbox and then presses the "Finish" button.

Note that this approach can be used only in an Enterprise project. You can read more about custom actions here:
http://www.advancedinstaller.com/user-g ... -page.html

For more information about the dialog editor feature, please see this page:
http://www.advancedinstaller.com/user-g ... ditor.html

If you don't want to (or cannot) use the dialog editor feature, then another approach is to add the Help MSI package as a prerequisite for the MSI package of the main application. You can read more about prerequisites here:
http://www.advancedinstaller.com/user-g ... requisites
http://www.advancedinstaller.com/user-g ... tware.html

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”