The intention of this tool is that an MSI or merge module (any Windows database) can be manipulated or created with a very few number of lines and without writing code. Any "common" manipulations are setup once and reused for all your MSI files.

All files are in text format so are easy to read and compare, you could easily create an MSI with a "handful" of commands (such as 2 line MSIs...). An HTML report is created when creating an MSI (this includes a file "verify" button). Also has a MSI dump and difference tool which you will find easy to read (and MAKEMSI can also process).

Features

• Automatic handling of files opened by applications (in use).
  
• If an install fails then prior changes will be undone (no half installs).
  
• Enables deployment (with or without elevated privledges) to all boxes in a network via Group Policy/Active Directory. Corporate customers will definately prefer (or in fact generally require) MSI based installers due to their ease of deployment.
  
• The automatic creation of XP system restore points at package install and uninstall.
  
• Self healing (repair) of files or registry entries.
  
• The advertising of complete applications (or parts) which allows installation on demand (resources not installed until required).
  
• Installation or uninstallation can be automated via command line parameters in a standard way (automatic support for silent or unattended installs).
  
• Allows merging of common "runtime files" (via Microsoft or other 3rd party merge modules).
  
• Configuration of MSI based products is supported by many mechanisms which are standard for all MSI installers.
  
• MSI files are databases which can be manipulated (by the end user) to tweak them or alterations can be done via separate transforms or options can be overridden from the command line. This can change install file and shortcut locations and control which features get installed plus much more.
  
• Microsoft Windows product logos require MSI based installers.

What's New

• The "PopupMessage()" sample code in "TryMeDllCustomAction.MM" was leaking handles (as reported by "grizzlyyh"), incorporated the fix provided.
  
• By default MAKEMSI now generates a warning when no final validation occurs so that it is more obvious that this is not a desirable stte of affairs. Override "VALID_MSIVAL2_COULDNT_VALIDATE_WARNING" to disable or alter.