inno setup

• Added .NET support (these cause an internal error if used on a system with no .NET Framework present):
  • Added new [Files] section flag: gacinstall.
  • Added new [Files] section parameter: StrongAssemblyName.
  • Added new constants: {regasmexe}, {regasmexe32}, {regasmexe64}.
• MinVersion parameter/directive change: if you leave one of the versions empty then it will use the default MinVersion for that platform.
• Pascal Scripting: Added new MinimizePathName support function.
• Added Unicode support: there's now a second version of Inno Setup available called Unicode Inno Setup. Key features of this version are its ability to display any language on any system regardless of the system code page, and its ability to work with Unicode filenames. Notes:
  • Unicode Inno Setup uses the existing ANSI .isl language files and you should not convert these to Unicode or anything similar since it does so automatically during compilation using the LanguageCodePage setting listed inside the language's .isl file. However, you do need to convert existing [Messages] and [CustomMessages] entries in your .iss files to Unicode if the language used a special „code page“ (character set).
  • The [Setup] directive ShowUndisplay­ableLanguages is ignored by Unicode Inno Setup.
  • Unicode Inno Setup is compiled with Delphi 2009 instead of Delphi 2 and 3, leading to slightly larger files. The source code however is still compatible with Delphi 2 and 3, and a non Unicode version will remain available.
  • Unicode Inno Setup and installers created by it require Windows 2000/XP or newer. The non Unicode version still works on NT/9×.
  • Existing installations of your programs done by non Unicode installers can be freely updated by Unicode installers, and vice versa.
  • Unicode Pascal Scripting notes:
    • The Unicode compiler sees type ‚String‘ as a Unicode string, and ‚Char‘ as a Unicode character. Its ‚AnsiString‘ type hasn't changed and still is an ANSI string. Its ‚PChar‘ type has been renamed to ‚PAnsiChar‘.
    • The Unicode compiler is more strict about correct ‚;‘ usage: it no longer accepts certain missing ‚;‘ characters.
    • The new RemObjects PascalScript version used by the Unicode compiler supports Unicode, but not for its input source. This means it does use Unicode string types as said, but any literal Unicode characters in the script will be converted to ANSI. This doesn't mean you can't display Unicode strings: you can for example instead use encoded Unicode characters to build Unicode strings (like S := #$0100 + #$0101 + ‚Aa‘;), or load the string from a file using LoadStringsFrom­File.
    • Some support functions had their prototype changed: some parameters of CreateOutputMsgMe­moPage, RegQueryBinary­Value, RegWriteBinary­Value, OemToCharBuff, CharToOemBuff, LoadStringFromfile, SaveStringToFile, and GetMD5OfString are of type AnsiString now instead of String.
    • Added new SaveStringsTo­UTF8File, and GetMD5OfUnico­deString support functions.
    • If you want to compile an existing script that imports ANSI Windows API calls with the Unicode compiler, either upgrade to the ‚W‘ Unicode API call or change the parameters from ‚String‘ or ‚PChar‘ to ‚AnsiString‘. The ‚AnsiString‘ approach will make your [Code] compatible with both the Unicode and the non Unicode version.
  • Unicode Inno Setup supports UTF-8 encoded .iss files (but not UTF-16).
  • Unicode Inno Setup supports UTF-8 and UTF-16LE encoded .txt files for LicenseFile, InfoBeforeFile, and InfoAfterFile.
  • QuickStart Pack: added ISPP predefined variable UNICODE.
• Thanks to Carlo Kok and Evgeny Karpov of RemObjects Software for their help related to Unicode support.
• QuickStart Pack: added ISPP functions Trim, and GetMD5OfUnico­deString.

• Added new [Registry] section ValueType: qword.
• Added new [Setup] section directive: SignTool, which makes it possible to further automate digital signing of Setup and Uninstall. See the help file for more information.
• The value of the AppVersion directive is now also used to set the MajorVersion and MinorVersion values in the Uninstall registry key when possible.
• /LOG: Now logs exit codes on [UninstallRun] entries.
• IDE changes:
  • Added new Tools | Configure Sign Tools… command.
• Command line compiler changes:
  • Added new „/S“ parameter to specify a Sign Tool.
• Added new [Files] section flag: sortfilesbyname.

• Improved support for right-to-left languages (Arabic and Hebrew):

Added new [LangOptions] section directive: RightToLeft. If set to yes, text alignment and reading order will be reversed (with some intentional exceptions), and controls will be arranged from right to left („flipped“).

• Added new [Setup] section directives: VersionInfoPro­ductName and VersionInfoPro­ductVersion.
• Changed the fixed Language field in Setup's version info from „English (United States)“ to „Language Neutral“.
• Uninstall now supports custom message constants ({cm:…}) like Setup.
• Right-to-left-related Pascal Scripting changes:
  • The control flipping that is performed when RightToLeft=yes is mostly transparent, normally requiring no changes to existing code. Controls created on custom wizard pages will be flipped automatically after the InitializeWizard event function returns, and controls created on custom forms will, by default, be flipped the first time the form is shown.
  • Changes to TSetupForm (the class used for custom forms):
    • Added RightToLeft Boolean property (read-only): True if right-to-left text alignment and reading order is enabled on the form. The RightToLeft [LangOptions] directive determines the value of this property.
    • Added FlipControlsOnShow Boolean property: If True (the default setting if RightToLeft is True), controls on the form will be flipped the next time the form is shown. After the form has been shown, the property is reset to False automatically.
    • Added ControlsFlipped Boolean property (read-only): True if the controls have been flipped.
    • Added FlipControlsIf­Needed method. This flips the controls immediately if FlipControlsOnShow is True, then resets FlipControlsOnShow to False.
  • Added new classes: TNewEdit, TNewMemo, TNewComboBox, TNewButton, TNewCheckBox, TNewRadioButton, and TNewListBox. On these classes, right-to-left text alignment and reading order is used when the parent TSetupForm's Rig­htToLeft property is True.
  • TNewStaticText: Added ForceLTRReading property. If set to True, the text will always be rendered with left-to-right reading order, overriding the parent form's RightToLeft setting.
• Other Pascal Scripting changes:
  • TNewStaticText: Added AdjustHeight method. This adjusts the value of the Height property to fit the text. Only useful when AutoSize is set to False.
  • Added new object UninstallProgres­sForm of class TUninstallPro­gressForm. Also added new event function InitializeUnin­stallProgressFor­m, which is called after the Uninstall progress form has been created and before it is shown. See the help file and the CodeClasses.iss example script for more information.
• Added workaround for bug in Windows Vista (still present in SP1): With UAC turned off, launching an uninstaller from the Programs and Features Control Panel applet and answering No at the confirmation message box would cause a „This program might not have uninstalled correctly“ dialog to be displayed, even though the uninstaller includes a proper „Vista-aware“ manifest.
• IDE changes:
  • The New Script Wizard now generates random unique AppId [Setup] section directives.
  • Added new Tools | Generate GUID command.
• QuickStart Pack: added ISPP functions GetMD5OfFile, GetMD5OfString and GetFileDateTi­meString.
• Minor tweaks.