Application Extension Mapping Dialog Box

InstallShield 2019 Express Edition

Use the Application Extension Mapping dialog box to add or modify the mapping between a file name extension and the program or interpreter that processes those files. This dialog box is launched when you click Add on the Application Mappings dialog box.

Application Extension Mapping Dialog Box Settings

Setting

Description

Extension

Type the file name extension that is associated with your application (for example, .abc).

To use a wild-card application mapping for an executable file, enter an asterisk (*).

Executable

Type the path, or click Browse to launch the Select Executable dialog box. This enables you to specify the executable in your project to which you want to map. Type the name of the executable file (.exe or .dll) or use the Browse button to search for the file. The executable file must be located on your Web server’s local hard drive.

Verbs

The Verbs section enables you to specify which HTTP verbs should be passed to the application.

•

All verbs—Select this option to include all verbs. This option passes all requests to an application.

•

Limit to—Select this option to specify the HTTP verbs that should be passed to an application. Separate verbs with a comma.

Script Engine (IIS 6 and earlier only)

If you want the application to run in a directory without Execute permissions, select this check box. This setting is intended primarily for script-based applications, such as ASP and IDC, that are mapped to an interpreter.

For a script-mapped application to run, either the Scripts Only or Scripts and Executables option must be selected for the Execute Permissions property. To allow only script-mapped applications to run, select the Scripts Only option. To allow both script-mapped applications and executable files (.exe and .dll) to run, select Scripts and Executables.

This setting applies to IIS 6 and earlier. IIS 7 ignores this setting.

Check that file exists (IIS 6 and earlier only)

To instruct the Web server to verify the existence of the requested script file and to specify that the requesting user should have access permission for that script file, select this check box.

If the script does not exist or the end user does not have permission, the appropriate warning message is returned to the browser and the script engine is not invoked. This option can be useful for scripts mapped to non-CGI executable files like the Perl interpreter that do not send a CGI response if the script is not accessible.

Note • Because the script is opened twice—once by the server and once by the script engine—there is some performance cost when this check box is selected.

This setting applies to IIS 6 and earlier. IIS 7 ignores this setting.

Application Extension Mapping Dialog Box

InstallShield 2019 Express Edition Help Library

April 2019