Adding a Web Deploy Package to a Suite/Advanced UI Project

InstallShield 2015

Project: This information applies to Suite/Advanced UI projects.

Edition: The Advanced UI project type is available in the Professional edition of InstallShield. The Suite/Advanced UI project type is available in the Premier edition of InstallShield. For information about the differences between these two project types, see Advanced UI Projects vs. Suite/Advanced UI Projects.

InstallShield lets you add Web Deploy packages (.zip) to a Suite/Advanced UI project. At run time, the Suite/Advanced UI installation deploys the Web Deploy packages to IIS Web servers or the cloud based on input from end users. The Web Deploy packages can be created through IIS or a Web application development environment such as Visual Studio.

To add a Web Deploy package to your Suite/Advanced UI project:

1. In the View List under Organization, click Packages.
2. Right-click the Packages explorer and then click New Web Deploy Package (.zip). The Select the installation file for this package dialog box opens.
3. Select the Web Deploy package file that you want to add to your Suite/Advanced UI project, and then click Open. The Add Files for This Package dialog box opens.
4. Specify whether you want to include additional folders and files with your package file, and if so, whether you want to include dynamically linked files. Typically a Web Deploy package is self-contained, and it requires only the .zip file.

InstallShield adds the package, plus any additional folders and files, in the Packages explorer.

Special Considerations for Configuring Web Deploy Packages in a Suite/Advanced UI Project

Life Cycle of Web Deploy Packages

Web Deploy packages are typically intended to behave similarly to first-time installations or to install over existing earlier or identical versions. As a side effect, Web Deploy packages do not handle uninstallation. Thus, Suite/Advanced UI installations do not offer maintenance for this type of package. It is recommended that you avoid creating a Suite/Advanced UI installation that combines one or more Web Deploy packages with one or more traditional packages (that do offer maintenance) as primary packages.

Suite/Advanced UI Properties vs. Hard-Coded Values for Web Deploy Configuration Settings

When you select a Web Deploy package in the Packages view, InstallShield displays package-related settings in the right pane. The Configuration area on the Common tab of the right pane includes several configuration-related settings for Web Deploy, such as the destination—which is often a remote server—and credentials. In addition, the Configuration area also includes settings for the parameters that are defined in the Web Deploy package’s parameters XML file. By default, InstallShield uses Suite/Advanced UI properties for all of the configuration settings so that end users can set them at run time through the wizard interface or the command line.

If you want to include a default value for a property, use the Property Manager view to specify that value for its corresponding property.

In some cases, you may want to use hard-coded values for one or more parameters. For example, if a particular Web Deploy parameter needs to be set to a specific value, you may want to replace the parameter’s default property name with a hard-coded value.

About the Wizard Interface for Configuration of Web Deploy Packages

When you add a Web Deploy package to a Suite/Advanced UI project, InstallShield automatically adds a predefined Web Deploy wizard page to your project for that package. The Web Deploy wizard page enables the end user to specify whether the package will be deployed to a local IIS server, a remote server, or a cloud-based server. It also uses a built-in Web Deploy–related action that enables the end user to load the configuration settings from a publisher profile file (.publishsettings).

If you want end users to be able to configure the parameters that are defined in your Web Deploy package’s parameters XML file, you can add controls to the wizard interface as needed, and associate those controls with the properties that are specified for the corresponding parameter settings in the Packages view.

See Also