Configuring Launch Conditions in .NET

Drawing QR Code 2d barcode in .NET Configuring Launch Conditions

You can specify launch conditions to restrict the computers your Web application can be installed on. For example, you can check for specific versions of Windows or verify that specific service packs are present. To add launch conditions, follow these steps: 1. Select your setup project in Solution Explorer. 2. Select the View menu, choose Editor, and then choose Launch Conditions. 3. The Launch Conditions Editor appears, as shown in Figure 13-2.

The Launch Conditions Editor has two related nodes:

13

Defines criteria to search for prior to installation. By default, this node contains Search For IIS. You can add file, registry, and Win dows Installer search conditions. Typically, you pair a search condition that determines whether a change is necessary with a launch condition that performs the change.

Based on a search condition or other criteria (such as the operating system version), the launch condition defines conditions that must be met prior to installation. Launch conditions can provide a useful message to the user if a requirement is missing. It can then automatically retrieve a Web page. By default, Web Setup Projects include conditions for the .NET Framework and Internet Information Services (IIS).

Typically, you must add an item to each of these two nodes to require a single compo nent. For example, if you want to verify that a specific Dynamic-Link Library (DLL) is present, you must create a search condition under Search Target Machine and store the result of the search in a property. Then you must create a launch condition that specifies the search condition s property, displays an error message to the user if the required file is missing, and optionally installs the required component from the Internet. To add a file launch condition, follow these steps: 1. In the Launch Conditions Editor, right-click Requirements On Target Machine, and then select Add File Launch Condition. The Launch Conditions Editor adds a search condition to the Search Target Machine node and a launch condition to the Launch Conditions node. The new search condition s Property value has a default name of FILEEXISTS1, which links it to the Condition property of the launch condition. 2. Rename both the new search condition and the new launch condition so that the names indicate the file you are searching for. 3. Select the new search condition and view the Properties window. Configure the properties as described in Table 13-1.

Description The name of the file to look for. Just specify the filename with extension, and not the folder.

Description The folder to search for the file in. You can search subfolders by specifying the Depth field. The number of nested folders within the speci

The name of the property that stores the results of this search. You specify this property name in the corresponding launch condition.

4. Select the new launch condition and view the Properties window. Configure the properties as described in Table 13-2.

Description The condition that must evaluate to true for installation to continue. By default, this is the name of a property assigned to a search condition, and if the search does find the required file or other object, the launch condition is fulfilled. You can specify more complex conditions to check for operating system version, service pack levels, and other criteria. For more information, read Configur ing Deployment Conditions later in this lesson. Optional. If the Condition is not met, the setup project retrieves this Uniform Resource Locator (URL) to install the required component. The message that is displayed to the user if the launch condition is not met.

13

To add a search condition, follow these steps: 1. Right-click Search Target Machine, and then select Add File Search, Add Registry Search, or Add Windows Installer Search. 2. Type a name for your search condition, and then press Enter. 3. With the new search condition selected, view the Properties window to config ure your search condition. The exact properties vary depending on the type of condition, but each allows you to specify that specific files, registry entries, or Windows Installer globally unique identifiers (GUIDs) are available. To add a launch condition that must be met prior to installing your Web appli cation, follow these steps: 4. Right-click Launch Conditions, and then select Add Launch Condition. 5. Type a name for your launch condition, and then press Enter. 6. With the new launch condition selected, view the Properties window to config ure your launch condition. Set the Condition property to match the Property value of a search condition or specify a different condition, as described in Con figuring Deployment Conditions later in this lesson. To download software to resolve the missing launch condition, provide a URL in the InstallUrl property. In the Message property, type a message to be displayed to the administrator who is installing your Web application. Administrators responsible for deploying and managing your Web applications can customize settings by editing your Web.config file. To enable simpler configuration at setup time, you can add custom setup wizard pages. With these pages, you can prompt users to custom-configure information, and then provide that information as parameters for custom actions. Combined, custom setup wizard pages and custom actions enable you to perform the following types of tasks at setup time: