InstallShield 2018 SP2 Premier Edition v24.0.573

Share

Program Name: InstallShield 2018 Premier Edition v24.0.573
Developer: Flexera Software
Homepage: http://www.flexerasoftware.com/products/installshield.htm
Release Date: May 7, 2018
Interface Language: Multilingual
Platform: Windows 2000, XP, 2003, Vista, 2008, 7，10，2016
File Size: 416.5 MB

InstallShield is the industry standard for authoring high quality Windows Installer and InstallScript–based installations, as well as Microsoft App-V packages. InstallShield 2018 helps you mitigate the risks of OSS code with a quick and easy scan of your daily build. You'll uncover OSS and IP compliance vulnerabilities before you ship, so your build becomes the first line of defense against future OSS data breaches.

Make a great first impression with your software. More than 100,000 application producers choose InstallShield to develop MSI and EXE installers, create Universal Windows Platform app packages and virtualize their apps. On agile or traditional development teams. Creating standalone offerings or complex suites. Deployed to the Windows Store or Nano Server.

Simpler, cleaner installs, upgrades and uninstalls with Universal Windows Platform support
- Develop MSI and EXE installers, and create Universal Windows Platform (UWP) and Windows Server App packages with minimal scripting, coding and rework.
- Prep applications for Windows Store and Nano Server.

Simplify virtual and cloud-based deployments
- Use multi-tier installation templates to deploy Web/server applications as a single cloud-ready package
- Deploy to hybrid cloud databases with Microsoft Azure SQL Database support
- Support enterprise application virtualization adoption by validating compatibility and creating Microsoft App-V packages

Most popular solution for Microsoft Windows and Visual Studio support
- The fast, easy way to build Windows installers
- Create installations directly within Microsoft Visual Studio
- Support enterprise customers with ISO 19770-2 software inventory tags, PowerShell scripting, and Sideloading of Windows Store Apps

Deliver a seamless customer user experience
- Create installers that match your company and product branding with InstallShield's Advanced UI editor
- Support continuous release processes by streaming the latest updates and patches at install time, ensuring users always install the latest version
- Localize installation text in 35 different languages

Future-proof your project from OSS vulnerabilities
- InstallShield* is the only installation automation solution to check for OSS security and IP compliance risks with one scan of your project.

What's New in InstallShield 2018:
Open Source Software Detection and Risk Assessment
Make InstallShield your first line of defense against potential OSS vulnerabilities. One fast, automated scan identifies OSS components in the project. Know your licensing obligations and make informed ship/no-ship decisions.

Windows Installer (MSI) Installations
Quickly and easily create Windows Installer (MSI) installations with advanced support for SQL databases, enhanced options in IIS view (Premier and Professional editions only), XML editing and much more with InstallShield’s intuitive graphical development environment.

Custom Bootstrappers to Bundle Universal Windows
Suite/Advanced UI installations bundle Universal Windows Platform app packages, MSI installers, EXE setups, Web Deploy packages and more into a single installer for simple installation by your customers. Enhancements offer more control for suite installation authors. Installers can be bundled with their dependencies, server configuration tasks, PowerShell scripts, and all the required components of a complex installation.

InstallShield Professional 2018 R2  Released: Sep 20, 2018
Support for MSIX - Now supports the latest deployment type from Microsoft - MSIX. Easily create MSIX packages or migrate existing MSI projects effortlessly. Use your existing projects to generate MSIX packages with just a few clicks.
Improved Designer Interface - Download the new InstallShield designer, with a fresh, modern look that simplifies creating an easy-to-use installation.
Dual Signing using SHA1 and SHA256 Digests - No more choosing between SHA 1 or SHA 256 to digitally sign the installers. Now digitally sign using both digests, a big help in supporting older Windows products.

InstallShield Professional 2018 Released: Jan 19, 2018
When creating a new QuickPatch project based on a previous QuickPatch project, and selecting a QuickPatch ISM that is in XML format, the Create New QuickPatch wizard displays the following error message:
<ProjectName>.ism is not a valid ism file. Please specify a valid QuickPatch project (.ism file) in the Existing QuickPatch Project field.
After using the New Language Wizard to add a new language to an InstallScript project, building with the InstallShield IDE successfully adds the new language to the media. However, performing the build on the Standalone Build System fails to add the language to the media, even after adding the new language to the Standalone Build.
Dependent files are not being included in the InstallShield package when building an InstallShield project with MSBUILD. However, dependent files are included when building the same project using the Visual Studio interface.
When you attempt to use COM extraction in InstallShield on a poorly written DLL, it will get stuck in an infinite loop during registration. InstallShield will hang indefinitely instead of stopping the process and displaying an error message after a certain amount of time has elapsed.
The features that install JRE50 and JRE7 in the InstallShield 2016 Prerequisite installer display incorrect names and descriptions. The feature name for JRE50 is displayed as ID_STRING102 and the feature name for JRE7 is displayed as ID_STRING94. The names of the features to be installed should contain a descriptive name reflective of the files that will be installed for that feature.
Specifying a Wizard Lite Wizard Format for the Suite UI displays a white strip along the top of each wizard page. The title and header image appears to be removed.
When customer tries to use a PowerShell custom action that uses the Import-Certificate cmdlet to install a certificate into the certificate store, the script works as expected outside of InstallShield, but when used in a PowerShell custom action, this cmdlet appears to do nothing.
In an InstallShield 2016 project, XCopyFile throws error 0x80070020. In an InstallShield 2014 project, XCopyFile returns 0.
When installing the FlexNet License Server (11.13.1.5) for use with a concurrent license, if you specify different port numbers for use with the HTTP port and the License Server Manager port, the ports are not saved and are reverted back to the default ports (8090 for HTTP and 20071-79 for License Server Manager port).
Microsoft SQL Server 2016 Express prerequisites fail to download.
When using Text Replacement in the SQL Scripts view, you are unable to replace a string with the same value but different case sensitivity. For example, finding the string testvalue and replacing it with TestValue fails; the script retains the value of testvalue. This occurs with the Preserve case option unselected. This behavior would be expected if Preserve case was selected.
InstallShield 2016 SP1 setup.exe installer can use LAAW_OPTION_WAIT_INCL_CHILD as a parameter for the original setup to wait for the termination of the clone process.
The Direct Editor displays a red signature column in the RegLocator table. When a second system search is configured that uses the RegLocator table instead of the Signature table, the Signature column in the RegLocator table is red.
When a new shortcut is created from the Project Assistant view, InstallShield automatically generates a short file name for the newly generated shortcut. If the newly generated shortcut is renamed from the Project Assistant view, a short file name is not generated for the renamed shortcut.
Calling a Basic MSI setup launcher from a command prompt and including parameters where the entire command exceeds 752 characters results in a “Setup Launcher Unicode Has Stopped Working” error. Although the error is seen, the MSI still launches and does contain all of the properties passed on the command line.
After applying a hot fix to an older version of InstallShield, using a relative path on the command line causes the setup to fail to launch.
When adding a scheduled task to a merge module project and including it in a Basic MSI project, build warning -6524 occurs.
Opening an InstallShield 2015 SP1 Basic MSI project in a Visual Studio 2015 solution causes hang and/or problems with the Visual Studio interface. The Solution Explorer becomes unresponsive.
The InstallShieldPrereqs_SQLServer.exe installer installs the SQL 2016 Express prerequisites to the SQL 2014 Express location, replacing the 2014 prerequisites.
When an MSI file is converted to an InstallShield project, the resulting .ism file does not reflect the Always Overwrite file settings that were set in the original MSI file.
When a suite project is run on Windows Server 2016, an error is encountered when attempting to enable an IIS Windows feature: runtime error 0x800f080c.
The XCopyFile() function is unable to copy a locked file when the LOCKEDFILE constant is passed. The message “Access is denied” is displayed.
If the ntmarta.dll file is located in the same folder as an InstallScript single .exe installer, it will cause a Unicode crash during setup initialization.
Checking for updates in InstallShield 2016 SP2 causes Software Manager to display “The product version is not registered on the server” instead of displaying the message that no updates are available.
Changing the brush color for the footer brush in a Suite project does not update the footer color for dialogs displayed in the InstallShield interface after a dialog has been viewed. However, the correct color is displayed: 1) if the user saves the project, then closes InstallShield and opens the project again, and 2) if the user changes the brush color prior to viewing a Wizard Page dialog in the IDE. The correct color is displayed at runtime; this is an interface problem.
A PowerShell custom action that uses the New㏒elfSignedCertificate cmdlet to create a certificate in the certificate store of the local machine does not behave as expected. The script works as expected outside of InstallShield, but when used in a Suite PowerShell custom action, the cmdlet does not create the certificate.
A suite installer that includes the Microsoft VC++ 2015 Update 3 prerequisite will crash on Microsoft Server 2008 if Microsoft VC++ 2015 Update 3 is already installed on the system.
When you include a right-to-left language and run a patch or minor upgrade (setup.exe), runtime error 2721 occurs based on binary table data.
InstallShield crash at build exception ACCESS VIOLATION (0xc0000005) at address <foo> trying to read address <dat>.
After applying an InstallShield hot fix, InstallShield MSI installers do not cache all language files, causing panels to display in the default language when launched from Add/Remove programs.
InstallScript MSI projects that use the new style InstallScript user interface type fail at runtime. The actual behavior varies slightly depending on if a setup launcher is included or not. In both cases the package does get installed.
Starting with InstallShield 2016, the Build Report Summary does not update any of the numbers for features, merge modules, prerequisites, dynamic links, or files. These all display 0. The number of components was also removed.
Change in InstallShield 2015 SP2 / 2016 is causing an issue with the UseDLL() function.
When using a differential media release for an upgrade, it can cause the “InstallShield Installation Information” folder to be missing the cached package, causing problems with repairs of missing files.
SETUPEXEDIR does not resolve to the expected value when passed to an InstallShield prerequisite.
Upgrading a Suite project from a previous version of InstallShield will remove the value from the string IDS_SUITEERROR_ABORTCONDITION.
Suite run using system context results in MSI parcel launch result: 80070003.
If the cryptbase.dll file is located in the same folder as a setup.exe installer file, it will be loaded during setup initialization.
Request that a registry convention be used as a condition for the Microsoft Visual C++ 2015 Update 3 redistributable instead of the msvcp140.dll file, which could be unreliable.

System Requirements
Windows Vista、Server 2008、7、Server 2008 R2、8、Server 2012、8.1、Server 2012 R2、10、Server 2016
Pentium III-class PC (500 MHz or higher recommended)
256 MB of RAM (512 MB preferred)
750 MB free space
Designed for XGA resolution at 1024 × 768 or higher



Download：
InstallShield2018PremierComp.exe
InstallShield2018PremierCompSP1.exe
InstallShield2018PremierCompSP2.exe