Released: Jul 10, 2024

2024 R1 中的更新

特性

• Added support for .NET Core Custom Actions - This release enables you to add the .NET Core type of custom action in the Custom Actions and Sequences view for a project to support the .NET Core based assembly files. The .NET Core type of custom action calls a public method in a .NET assembly that is written in a managed code such as Visual Basic .NET or C#.
• Enhanced Database Import Wizard for SQL scripts
  • You can use the Database Import Wizard in the SQL Scripts view to import your database settings and generate an SQL script file, based on the configured settings and options.
  • In this release, the Database Import Wizard has been enhanced to include SQL Server Management Objects (SMO). The incorporation of SQL Server Management Objects enables you to import database objects and generate an SQL script file more accurately and efficiently. This enhancement also enables you to resolve legacy script issues reported by customers.
• Added the ability to prevent multiple executions of Setup.exe
  • This release introduces a new setting named, Prevent Multiple Launches, on the Setup.exe tab for a release in the Releases view, which allows you to specify whether you want to prevent the multiple launches or executions of the setup.exe file during the same period. The following are the available options:
    • Yes - Selecting this option prevents the multiple launches or executions of the setup.exe file during the same period.
    • No - Selecting this option allows the multiple launches or executions of the setup.exe file during the same period.
    • By default, this setting is set to No.
• Run a Suite Installation Silently Without Downloading Updates - In this release, you can now use a new command-line parameter named /skipupdate to configure a Suite/Advanced UI silent installation to instruct the installer to skip the download of any updates and proceed with a silent installation, instead of automatically forcing a user to apply the downloadable updates.
• Added the ability to hide property value in verbose log
  • In this release, you can now hide the required property value in the verbose log file using the MsiHiddenProperties property.
  • This enhancement involves setting the required property as a value of the MsiHiddenProperties property using the Property Manager view of the Behavior and Logic. As a result, the required property value, which is defined in the Install properties setting for a selected package of the Chained .msi Packages explorer in the Releases view of the Media, is not visible in the verbose log file.
• Added the ability to specify EV/OV token password using command line - In this release you can now specify the EV/OV token password via the cert_password-an optional parameter in the command line build-to sign the files in the project.
• Added the ability to display proper image at 125% and 175% scaling - In this release you can now display the proper or correct size of an image on the Suite Loading screen during an installer installation when the Windows scale is set to 125% and 175%.

修补程序

• When the Signing Type setting was set to the Custom option, the Sign files in package setting failed to digitally sign the package payload files.
• When the Custom option was selected in the Signing Type setting, the .mst files were digitally signed twice, which led to an increase in the build time.
• For setups that were configured with the registry and file permissions options, a vulnerability was reported in the Basic MSI and InstallScript MSI (64-bit) setups.
• The InstallShield interface failed to display the correct characters if the Beta: Use Unicode UTF-8 for worldwide language support checkbox was selected in the Windows locale settings.
• An InstallScript MSI project build failure was observed with the ISDEV : fatal error -1027: Failed signing _isuser_0x0409.dll error message when the InstallScript User Interface Type setting was set to the New Style (Requires Windows Installer 4.5) option.
• A failure was observed when returning a borrowed license.
• After a successful silent installation, the ResultCode value in the [ResponseResult] section of the setup.log file failed to update.
• Usage of the InstallShield Self-Registration (ISSelfReg) method to register the .dll files in a project led to a vulnerability.
• While launching the installer in the Japanese language, if the user name included multiple byte characters, the image failed to appear in the Sd dialog.
• The database column, which was initially set to the MAX value, changed to 0 value while importing the database to the SQL Server view. This led to a setup installation failure with the Length or precision specification 0 is invalid. (1001) error message.
• After rebooting, the installer installation failed to remove all files from the temp directory due to the included prerequisites.
• Using the /tempextractpath argument failed to extract files to a customized directory.
• Deletion of the SRCDIR source folder led to the display of the Please insert disk 1 that contains the file data2.cab prompt message during an InstallScript installer repair.
• Documentation failed to mention the non-operational behavior of the /extract_all command-line parameter when used in the Setup Command Line box on the General Options panel of the Release Wizard.
• Documentation failed to describe the requirements for the proper functionality of the system search for the default value of the Registry key.
• The official Microsoft terminology for .NET attributes failed to appear consistently in the documentation.