Advanced Installer 4.1 Release Notes

On June 21st, 2006 Caphyon Ltd. is proud to announce the release of Advanced Installer 4.1 in Free, Professional, Java, Enterprise and Architect editions. This release is available for download on the Advanced Installer website.

Version 4.1 adds a comprehensive set of command line options, enabling a great degree of scripting and automation in the package, patch or merge module creation process. Also new is the multi-file prerequisites support, which allows your packages to ensure the installation of almost any third party software they depend on.

New features

  • Command-line options for most used UI actions, enabling a greater degree of scripting and automation
  • Ability to run a script file of commands on a project
  • Multi-file Prerequisites

Enhancements

  • Component-less Merge Modules
  • Project duplication enabling reusing for another application
  • Automatically synchronizing control size and position between dialogs
  • Automatically synchronizing dialog size and position in sequences
  • Automatically removing other (incompatible) versions of the same product when running a package from Advanced Installer
  • Searching for the (Default) registry value
  • New parameter to the Updater /silent command that will bypass the frequency check
  • Java sample code integrating the Updater with the MainFrame of a Java application

Bug fixes

  • Directory name not translated correctly when marked for translation
  • Event for chain not detected correctly in ControlEvent dialog (tab)
  • Events for main chain could not be edited
  • Compatibility issue with older projects that have the ProductCode as plain GUID without language code
  • DLL files built for x64 couldn't be marked as self-registrable
  • System Library Path of Java product not working
  • UI Custom Actions not sorted under a standard action
  • Update picture size on RadioBtn resize
  • Merging more than 1 merge module in a msi with no files caused install time error
  • When using multiple merge modules that each have file associations the wrong icon can be registered for one or more of the file types
  • Build error when using Action Text for custom actions