Skip to content

Project Properties - Web Application

The Web Application properties page provides configuration options specifically relating to web applications.

Web Application Name

This is the name of the web application in the Web Application Administrator. The value displayed is read-only and is read from the current workspace's global.asa file.

Virtual Directory

This value is a copy of the virtual directory name that was created when the web application itself was created. The Studio keeps a copy of this value so that it can be passed as a parameter to tools launched from the Studio's Tools menu.

It is the developer's responsibility to maintain this value so that it is synchronized with the web application's actual virtual directory name.

For more information, refer to Configuring the Tools Menu.

Session Timeout

This value refers to the IIS session timeout value (in minutes) that applies to the web application. This value is written to the web application's global.asa file each time the web application is compiled.

HTML Test Run File

This provides the URL in the workspace's AppHtml folder for the HTML file used by the Studio to test run the web application.

Disable WebApp Support

Check “Disable Web Application” to disable the current workspace’s web application. This is equivalent to disabling a web application via the Web Application Administrator (Properties).

You must be running the Studio with administrator rights in order to disable or enable a web application in this way.

Disabling a web application will stop the WebApp.exe from running in the process pool that is managed by the Web Application Administrator. The WebApp.exe process pool is not launched again until the web application is enabled.

Disabling a web application is useful at certain times. For example:

  • If you want to modify the database, you may need to shut down all applications that open tables from the database.
  • If you are developing many web applications on the same machine, you may wish to disable several of the web applications to save resources.

When a web application is disabled, it cannot be run in the normal way, but you will still be able to run a disabled web application in the Studio’s debugger. Disabling a web application does not prevent you from test running it in the debugger.

The Studio’s Workspace Dashboard displays the enabled/disabled status of the workspace’s web application. Clicking on this item in the Dashboard will open the Project Properties dialog, allowing you to toggle the enabled/disabled state.

Note: Disabling a web application is different from “Stopping” a web application. When you “stop” a web application (from within the Web Application Administrator), the web application pool will be unloaded; however, the web application would be automatically re-started whenever you reboot your machine or whenever you re-compile your WebApp.exe. Therefore, “stopping” a web application is only temporary. When a web application is disabled, the process pool remains unloaded until the web application is explicitly enabled.

Web Application Setting Analysis

The Studio performs the following analyses on your web application settings:

  • WebApp Name (as stored in Global.asa) not registered in WebApp Administrator.
  • WebApp Name (as stored in Global.asa) is not a case-sensitive match to the name registered in the Administrator.
  • The registered WebApp in the WebApp Administrator points to a different WebApp.exe location.
  • The registered WebApp does not use process pooling (warning).
  • Global.asa is missing.
  • The WebApp Name can be located in Global.asa.

If any of these tests indicate a problem, then the problem is reported in the Web Application Settings Analysis section. The Register WebApp operation (below) can be used to repair these settings.

Register WebApp

This will activate the Register Web Application dialog.

  • Update the webapp registry with the entered web application name and default web application settings.
  • Create a virtual directory using the entered virtual directory name.
  • Create a Global.asa (if needed) and set the web application name inside it.
  • Set parameters in the web application’s .cfg file.

See Also