Released: Oct 18, 2022

20.0 での更新項目

機能

• New Repackager Automation and MSIX Compatibility Framework enables your team to automatically analyze and convert applications to MSIX.
• Support for parallel downloading and installation (with progress) of prerequisites.
• Customize location when running Microsoft PowerShell scripts.
• PowerShell automation support for adding 'PowershellScriptFile'.
• PowerShell automation support for adding chained packages.
• Security improvement: You can now protect EXE setups from loading tampered versions of 'decoder.dll' file.
• Added support for synchronizing paths written in INI with APPDIR path and setup install type.
• Added new Installer Analytics parameter to distinguish between installs and uninstalls.
• 'Run PowerShell script file' custom action now supports script parameters.
• Improved the 'Select a Component' dialog.
• PowerShell custom actions are now digitally signed by default.
• Added 'Add/SetUwpAppxPackageProperties' command line support for Microsoft Windows Store App and Modification Package projects.
• Generate a new unique folder name for New, Duplicate, and Copy/Paste build operations.
• Updated package-related icons and images for a refreshed look and improved rendering on high DPI.
• Now shows warnings when using some Repackager options.
• Added symbolic link support in MSI Editor Mode.
• Added the ability to synchronize file extension icon between MSI and MSIX build.
• Added new option to disable WinUI transitions.
• Improved field validation in Repackager GUI.
• Improved 'copy file/folder' action.
• Added a predefined prerequisite for Python installer.
• Updated MSIX platforms to Windows 11 version 22H2.
• Updated Microsoft .NET and .NET Core prerequisites to latest versions (6.0.10 & 3.1.30).
• Added predefined launch condition for Windows 11 version 22H2 x64 (Preview).

不具合の修正

• File search failure when using the "Entire Project" criteria.
• The translation string cannot exceed 260 characters.
• Visual glitches between dialogs on the Surface theme.
• Custom name is still used when the "Register product with Windows Installer" option is disabled.
• PowerShell script signing fails if "ProductName" contains double quotes.
• Control conditions for the "Styled Progress" control do not work.
• The "Synchronize property's value with the value from a JSON file" option displays malfunction on high DPI resolutions.
• Invalid input error when pressing the TAB key on the Set Installer Property custom action field.
• The prerequisite's search done by custom executable doesn't work.
• The custom action from the SQL/ IIS/ Users and Groups browse gets deleted because the focus is on the custom action instead of the browse.
• On high DPI displays, the PowerShell custom action execution properties are not clearly visible.