Getting Started with InstallAware Studio for Windows Installer

Getting Started with InstallAware Studio for Windows Installer

Introduction

InstallAware Studio for Windows Installer is a professional setup-authoring tool that builds MSI and EXE installers for Windows applications. This guide walks you through the essential steps to create your first installer, configure common project settings, add files and resources, and build and test the package.

Prerequisites

• A Windows development machine (Windows 10 or later recommended).
• InstallAware Studio installed (trial or licensed).
• The application files you want to package (binaries, config files, assets).
• Administrator privileges to install and test MSI packages on target machines.

1. Create a New Project

1. Open InstallAware Studio.
2. Click File > New Project.
3. Select Windows Installer (MSI) project type and choose a template (Empty Project, Simple Install, or Application Upgrade).
4. Enter a project name and location, then click Create.

2. Configure Product Details

• Product Name: Human-readable name for the installer.
• Product Version: Use semantic versioning (e.g., 1.0.0).
• Manufacturer/Publisher: Company or author name.
• Product Code & Upgrade Code: InstallAware generates GUIDs automatically; keep them unless you need custom GUIDs for upgrade behavior.
  Set these under the Project > Project Settings or the Product Information pane.

3. Add Files and Folders

1. Open the Files and Folders view.
2. Add your application files to the appropriate destination folders (e.g., Program Files\YourApp).
3. Set component options (key file, permanent, shared) as needed to control uninstall and component rules.
4. Include prerequisites (VC++ runtimes, .NET frameworks) in the Prerequisites section if your app depends on them.

4. Define Shortcuts and File Associations

• Create desktop and Start Menu shortcuts: right-click the executable in Files view > Create Shortcut.
• For file associations, use the File Types editor to register extensions and associate an icon and open command.

5. Add Registry Entries and INI Settings

• Use the Registry editor to add keys/values required by your application.
• INI file operations can be configured using the INI editor if your app uses INI configuration.

6. Configure Custom Actions and Install Logic

• Use Custom Actions to run scripts, EXE files, or DLL functions during install/uninstall.
• Insert conditions to run actions only for specific Windows versions, install types (per-machine vs per-user), or upgrade scenarios.
• Use InstallAware’s scripting language for more advanced logic (silent install parameters, license checks, license key validation).

7. Set Up Upgrade and Versioning Behavior

• Configure Major/Minor upgrade rules in Upgrades settings.
• Maintain the Upgrade Code across versions to enable Windows Installer to detect and perform upgrades.
• Change Product Code for major upgrades when changing the installation footprint significantly.

8. Build the Installer

1. Select Build > Build Project.
2. Choose output type: MSI, EXE, or Suite (EXE bootstrapper including prerequisites).
3. Monitor the build log for warnings and errors; resolve any issues reported.

9. Test Installation

• Install the generated MSI/EXE on clean VMs or test machines.
• Verify file placement, shortcuts, registry entries, and app launch.
• Test uninstall and upgrade scenarios, including rollback behavior on failed installs.

10. Create a Silent/Unattended Install

• Expose command-line switches (e.g., /S, /qn) and properties for silent installs.
• Document public properties (e.g., INSTALLDIR) so IT teams can customize installs.
• Test silent installs and uninstalls in your QA environment.

Troubleshooting Tips

• Use InstallAware’s verbose logging option to capture installer actions.
• Check component key files and GUIDs if files are not being installed or removed properly.
• Resolve shared DLL reference counts by marking components correctly (shared vs. permanent).
• Validate MSI with tools like Orca or Windows Installer XML (WiX) tools for advanced inspection.

Best Practices

• Keep one component per key file to avoid component rules conflicts.
• Use relative paths in the project to make version control and CI builds simpler.
• Include prerequisites in the bootstrapper to reduce user friction.
• Regularly test upgrade paths between released versions.

Conclusion

Getting started with InstallAware Studio for Windows Installer involves creating a new project, adding your application files, configuring product and upgrade settings, defining shortcuts and registry entries, and building and testing the installer. Follow the steps above, apply the troubleshooting tips, and adopt best practices to produce reliable MSI/EXE installers for your Windows applications.