How Do I Build MSI, UWP and WSA App Packages from the Same Project? Find Answers in the What’s New in InstallShield 2016 Q&A

The webinar, What’s New In InstallShield 2016, highlighted the important features in this new release, including compatibility testing for Microsoft’s Universal Windows Platform, mapped MSI relationships, customizable Windows tiles and more. It also provided a great Q&A session, which resulted in the important information below. Need more? Don’t forget the Flexera Community or you can contact us directly. 1. Will the packages built with Insta…

October 14, 2016 Revenera

InstallShield 2016 Supports Microsoft Windows 10 Anniversary Update Announcement for Desktop Bridge

The new release of InstallShield 2016 supports the transition to Microsoft’s Desktop Bridge (formerly known as Project Centennial) and Windows Server Apps (WSAs) with automatic compatibility tests and continuous build capabilities. “Working in parallel with Microsoft, we are making it easy to transition existing InstallShield MSI projects to build Universal Windows Platform and Windows Server App packages. InstallShield is the only product that e…

September 16, 2016 Revenera

Responding to Missing Source File Errors in InstallShield

If the build process cannot find a source file because it has been renamed or deleted, the build process returns error –6103 (“Could not find file file”) and –1007 (“Cannot copy source file to target directory”). Two features of InstallShield can help you work with source files—path variables and dynamic file linking. Path variables are variables used by the InstallShield build process to represent the locations of source files on the development…

July 26, 2016 Revenera

Adding Configurations with the InstallShield Automation Interface

You can use the InstallShield Automation Interface to add product configurations and releases to an InstallShield project using the AddProductConfig and AddRelease methods. After adding a product configuration or release, you specify its properties (the properties you would ordinarily enter in the Release Wizard) using the individual automation properties of the ISWiProductConfig or ISWiRelease object you created. For example, suppose you want to…

July 12, 2016 Revenera

InstallShield Tip: Was the MSI Setup Launched from Setup.exe?

In a basic MSI project created with InstallShield, creation of the Setup.exe setup launcher is optional. If your build configuration is set up so the MSI database is external to Setup.exe and if the target system has the Windows Installer service present, a user can launch your MSI file directly to initiate the installation. In some cases, you might want to determine whether the user launched your setup from the setup launcher or from the MSI dat…

June 23, 2016 Revenera

How to Create an Internet Shortcut with InstallShield

Since the Windows Installer service does not directly support Internet shortcuts, it’s not possible to create a shortcut to a URL in the Shortcuts/Folder view of the IDE. However, an Internet shortcut is only a text file with the .url extension. You can create an Internet shortcut on the user’s machine by installing a .url file with the appropriate contents. For example, to create an Internet shortcut that launches the InstallShield web sit…

June 9, 2016 Revenera

Basics of MSI Custom Actions

MSI supports a variety of custom actions and InstallShield can assist you in working with those actions. Types include: Launching executables Calling DLL or script functions Setting property-table properties and directory-table properties Error actions There are two steps involved for each custom action you want to use: Define the action: specify what the action does (launch an executable, call a DLL function, set a property, and so forth) and…

April 19, 2016 Revenera

InstallAnywhere Flat Certificate Exports for Windows Signing

A “flat” certificate, without the certificate chain path included, is required for signing with InstallAnywhere. In order to sign a Windows target using InstallAnywhere, it is necessary for the certificate to be exported flat. In other words, the certificate chain path cannot be included. This is normally a default option, so it must be disabled. If the certificate chain path is included, the builder will report: “Code signing failed with followi…

February 4, 2016 Revenera