Application and Virtual Directory Settings

Enter a name for the application or virtual directory.

When you type a value for this setting, you are creating a string entry and setting its initial value for all of the languages that are currently in the project. As an alternative to typing a new value, you can click the ellipsis button (...) in this setting to select an existing string. For more information, see Using String Entries in InstallShield.

Note:This setting applies to applications but not virtual directories.

To set the ASP.NET version for the application, enter the complete version number, or select it from the list.

For example, to specify version 2 of ASP.NET, type 2.0.50727. To specify version 1.1 of ASP.NET, type 1.1.4322.

If you specify an ASP.NET version for a Web site, IIS uses that same version number for any of the Web site’s applications.

Important:If your installation may be run on a Windows Vista or later system, you may not want to set the ASP.NET version. Also note that if you specify version 3 of ASP.NET, an error occurs at run time. For more information, see Setting the ASP.NET Version for a Web Site or Application.

To set the ASP.NET application registration option with Internet Information Services (IIS), select one of the following options:

This setting identifies the local path or network directory path that stores the default files for your application or virtual directory.

By default, the files are stored in IISROOTFOLDER.

\\server\share

Tip:Each application or virtual directory should have a unique physical path, especially if it is going to be installed on a Windows Vista or later system or a Windows Server 2008 or later system. To learn more, see Run-Time Requirements for IIS Support.

Specify whether you want to provide end users with read access to the application or virtual directory.

Specify whether you want to allow end users to see all the virtual directories and subdirectories below this application or virtual directory.

To associate the selected virtual directory with an application, specify the application name.

When you type a value for this setting, you are creating a string entry and setting its initial value for all of the languages that are currently in the project. As an alternative to typing a new value, you can click the ellipsis button (...) in this setting to select an existing string. For more information, see Using String Entries in InstallShield.

Note:This setting is available for virtual directories, but not for applications.

If the virtual directory was created in InstallShield 2009 or earlier and then upgraded to the current version of InstallShield, this setting is displayed. Otherwise, this setting is not included.

To customize the directory’s application mappings, click the ellipsis button (...) in this setting. This opens the Application Mappings dialog box, which enables you to add, edit, and delete a mapping between a file name extension and the application that processes those files.

Specify the number of minutes that a session can remain idle before the server terminates it automatically. If the end user does not refresh or request a page within the timeout period, the session ends. The default value is 20 minutes.

Specify what level of program execution is allowed for the selected application or virtual directory. Available options are:

Specify whether you want to allow users to establish an anonymous connection. If you do want to allow anonymous connections, also enter the appropriate Windows user account information.

If you do not need the Web server to confirm the identity of end users before they can access the content, select No for this setting.

If you are enabling anonymous connections, type the name of the anonymous account.

Specify whether you want to enable the basic authentication method for collecting user name and password information for end users who access the application or virtual directory.

Important:With the basic method of authentication, user names and passwords are not encrypted when they are transmitted across the network. An unscrupulous end user who has network monitoring tools could intercept user names and passwords.

To customize HTTP errors that are sent to clients when Web server errors occur, select the ellipsis button (...) in this setting. The Custom Errors dialog box opens, enabling you to specify the page that should be displayed for one or more HTTP errors.

Administrators can use generic HTTP 1.1 errors, detailed custom error pages that IIS provides, or your own custom error pages that are you including in the installation.