• Several dozens of custom actions let you do most everything you want: read/write from/to Windows registry, create Windows & Internet shortcuts, execute multiple programs, open document files and Web pages, display message boxes and readme texts in Rich Text Format (WYSIWYG), ask your end users for folders, options, passwords, set file destination and conditions on extraction, register shared files and self-register files, check file properties and integrity (CRC32), prompt users for password and information, use If/Then/Else and Goto statements, restart computer, install Windows Installer MSI or MSP, show an information panel with variables...

Add New Custom Action

  • Visually manage custom actions using the powerful editor. Add, remove, modify, move, copy/paste single or several actions, import/export custom actions without requiring any additional knowledge. Even if custom actions are similar to scripting, you have not to learn any special language.
 
  • Change file attributes; detect EXE bitness (32-bit or 64-bit); create custom folders; remove specific or multiple files; display license agreements; remove folders; check for files, folders and registry key's existence; execute document (show Web pages) files; read or write .ini entries; copy or rename files; add extra commands for the uninstaller, read existing XML files and data, write XML entries (nodes, attributes) and modify XML files, store information into external files...
     
  • Ability to work with variables: you can use variables to store data, read/write from/to the Windows Registry, read/write to .ini files, perform conditional (if/then/else) tests, use goto label jumps... Paquet Builder includes a variable manager that lets you add or remove your own variables.
     
  • Possibility to add an uninstaller to your packages: end users can remove changes your package made (unpacked files, registry entries, shortcuts, self-registered files...). This uninstaller is fully customizable and useful if you create a setup routine for your software program. You may even add uninstall commands and custom actions to remove additional files or run external programs, in order to perform additional cleaning.
     
  • Build 32-bit and 64-bit (x64) packages that can install 64-bit applications or access 64-bit Windows registry.
  • Group your files into components and let your users decide which ones should be installed on their computer. Components are managed using the file manager, and have special properties that allow you to control their behavior (whether associated files will be unpacked or not for instance).
     
  • Determine the destination folder for each file (you can extract ActiveX controls to the Windows System folder for example) and optionally you can associate a conditional variable to each file that decides whether the file should be extracted or not. It allows you to group your files into components as in setup routines.

File Properties

  • Packages can register shared files and self-registered ActiveX and DLL files. The uninstaller can safely remove them if they are not used anymore.
     
  • Easily and visually manage shortcuts and registry entries to create. You can moreover import/export .REG files.
     
  • Read the file destination path from the Windows Registry, register more ActiveX controls, run BAT files, execute multiple Setup programs and then remove all temporary files, display destination folder in a shell window after extracting files, show a Web page after a successful extraction, show a final dialog or message box, run an additional program (a.k.a. "final task") or display a file when the package closes.
     
  • In addition to custom actions, you can run a document or an executable file, display prompt messages, create Windows shortcuts, write custom entries in the Windows registry if you do not want to work with custom actions.
     
  • Support for Microsoft Windows Installer (MSI) databases and patches (MSP): Paquet Builder provides you with tools to automatically configure your setup project for executing these setup procedures instead of a traditional setup program.
     
  • Install several Windows Installer MSI setups or MSP patches back to back. Check for the presence of the Windows Installer service.