AdminStudio at AppDeploy.com
User Forum: Package Creation
Packages: Application Specific Deployment Tips

Installation Authoring

From within InstallShield author you can browse for your project file (the default directory is %temp%). Selecting the INC file created in the previous section launches the import wizard. The details of your package are displayed and the default path and filename for the ISM (Author Project) file to be created are presented. Before importing, some advanced features may be enabled (they are by default) that are worth mentioning here:

• Enable path variables in the converted project file. This will help to move the project file from one machine to another.
• Minimal UI in the created MSI file. When run, only the InstallShield welcome dialog will be displayed.
• Replicate HKCU settings. This will copy all entries in HKCU to HKU\.Default, so that the entries are available for all users.

A summary of your selections are presented on the next dialog along with an option to create an MSI file after creating the setup project.

The actions taking place scroll by quickly in a window at the bottom of the InstallShield Author display (see image below).

Once converted to an .ISM project you can make any customizations you wish in the InstallShield Author program. The editor provides a very intuitive interface to the many elements that make up your MSI package. Much time has obviously been spent on the look of these tools and it definitely shows. Throughout your use of these tools you will see graphical "Feedback" links that bring you to a form on the InstallShield web site. This certainly gives the impression that your opinion matters and that taking the time to share it with them may be well worth your time.

A view reminiscent of Microsoft Outlook provides an expandable tree on the left pane with varying degrees of options, fields and help on the right. With the vast amount of options possible with Windows Installer, the help and best practices information integrated into this interface makes all the difference. In the preferences window you can choose one of three displays for this program:

• The "Classic" style closely resembles the structure of previous versions of InstallShield software.
• The "New" style provides a task-oriented way for you to attack your setup project.
• The "AdminStudio" style (the default style for Author) provides a task-oriented checklist designed specifically for administrators. The Help Library's table of contents is based on this style, although the content is applicable to all view styles.

There is even an option to enforce best practices that causes Author to monitor your setup design in order to ensure that you comply with Setup Best Practices.

Yet another nice wizard, the Release Wizard, walks you through compiling your MSI setup for distribution. Your are prompted for what media type you will be distributing your setup on and can choose to have the source files compressed within the MSI or to have them remain uncompressed (as you would normally see in a CD distribution). It also allows you the option of creating a setup.exe to launch the MSI setup, this executable can also be selected to detect and install the Win9x MSI engine, or the Windows NT MSI engine, as needed. If using MSI 2.0 you can choose to delay the MSI engine reboot until after your setup has completed. 

You can choose to have any missing MSI engines installed from source contained within the setup.exe or from the Internet. The setup.exe also may be digitally signed and/or password protected.

Take your MSI files and check them for conflicts against one another in ConflictSolver…

Read on...

[Previous]  1  2  3  4  5  6  [Next]

• Log on
• Register
• Survey Results