[This is preliminary documentation and subject to change]

Creating Applications

To create an application, you designate a directory as the starting point (application root) for the application. You can then set properties for the application. Each application can have a friendly name; this name appears in the IIS snap-in and gives you a way to distinguish between applications. The application name is not used anywhere else.

You can remove a directory from the application boundaries, so that requests to files in that directory and its subdirectories cannot start the application. Removing a directory from an application boundary does not delete the directory from either your Web site or from your computer's hard disk.

To create an application

In the IIS snap-in, select the directory that is the application starting point. You can designate the home directory of a Web site as an application starting point.
Open the directory's property sheets, and click the Home Directory, Virtual Directory, or Directory tab.
Click the Create button.
In the Application name text box, type a name for your application.

note Note If you see a Remove button instead of a Create button, an application has already been created.

To remove a directory from the application

In the IIS snap-in, select the directory you want to remove.
Open the directory's property sheets, and click the Home Directory, Virtual Directory, or Directory tab.
Click the Remove button.

Tips

To stop an application and unload it from memory, click the Unload button. If the Unload button is dimmed, you are not in the application's starting point directory.
To dissociate this home directory from an application, click the Remove button.
Select the Run in Separate Memory Space (Isolated Process) check box to run the application in a process separate from the Web server process. Running an isolated application protects other applications, including the Web server itself, from being affected if this application fails or stops responding.

To set permissions for an application

Set permissions to None to prevent any programs or scripts from running.
-Or-
Set Scripts only to enable applications mapped to a script engine to run in this directory without having Execute permission set. Use Script permission for directories that contain ASP scripts, Internet Database Connector (IDC) scripts, or other scripts. Script permission is safer than Execute permission because you can limit the applications that can be run in the directory. For information about making an application a script engine, see the App Mappings Property Sheet property sheet.
-Or-
Set Scripts and Executables to allow any application to run in this directory, including applications mapped to script engines and Windows binaries (.dll and .exe files).