|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.|
Web Site Administration Tool Overview
The Web Site Administration Tool lets you view and manage the Web site configuration through a simple Web interface.
Tabs and Additional Information
The following links provide more information about how to work with the Web Site Administration Tool:
Web Site Configuration
Web site configuration settings are stored in an XML file named Web.config, which is located in the root folder of the Web site. The Web Site Administration Tool lets you change your site configuration without having to manually edit the Web.config file. The first time that you use the Web Site Administration Tool to administer a specific Web site, if no Web.config file exists, the Web Site Administration Tool creates one. By default, the Web Site Administration Tool also creates a database in the App_Data folder of the Web site to store application services data, such as membership and roles information. For most settings, changes that are made in the Web Site Administration Tool take effect immediately and are reflected in the Web.config file.
Default settings for a Web site are automatically inherited from any configuration files that exist for the computer or for the Web server as a whole. For example, the Web server might have default settings that apply to all sites on that server. Using the Web Site Administration Tool, you can create and modify settings for your specific Web site that are not inherited, and you can override the inherited settings as allowed by the site-wide settings. If the setting has been inherited and cannot be overridden, it appears dimmed, to indicate that it is disabled, in the Web Site Administration Tool.
The Web Site Administration Tool is included with the Microsoft Visual Web Developer Web development tool. In order to use the Web Site Administration Tool to administer a Web site, the user credentials for the user account under which you are running Visual Web Developer must have Read and Write permissions to the Web.config file and the App_Data folder of the application being administered. If you cannot manage the configuration for the Web site using the Web Site Administration Tool, contact the system administrator.
The Web Site Administration Tool features a tabbed interface that groups related configuration settings within each tab. The tabs and the configuration settings that the tabs manage are described in the following sections.
Use the Security tab to manage access rules to help secure specific resources within the Web site and to manage user accounts and roles.
You can specify how the Web site is used—either from the Internet (publicly) or from an intranet (on a local area network). This in turn indicates the type of authentication mode that the Web site will use. Internet Web sites use the ASP.NET membership system, where you define individual user accounts. ASP.NET uses a security system to restrict access to specific user accounts or the roles to which the user accounts belong. Intranet Web sites use Windows authentication, where users are identified by their Windows logon information.
Use the Application tab to manage a variety of settings related to the Web site, including the following:
Application settings, which are name/value pairs that you want to store centrally and access in code from anywhere in the Web site.
SMTP settings, which determine how your site sends e-mail.
Debug and trace settings.
Offline and online settings, which take the Web site offline (shut it down) to perform maintenance or to bring a new Microsoft SQL Server Standard edition database online.
Use the Provider tab to test or assign providers for membership and role management for the Web site. Database providers are classes that are called to store application data for a particular feature. By default, the Web Site Administration Tool configures and uses a local Microsoft SQL Server Standard Edition database in the App_Data folder for the Web site. Instead, you can choose to use a different provider, such a remote SQL Server database, to store membership and role management.
How to Use the Web Site Administration Tool
Using the Web Site Administration Tool is similar to using other forms-based Web sites. The general procedure is to open the Web Site Administration Tool, select the appropriate tab, and then adjust the settings that are available on that tab. Most changes take effect immediately.
How to Access the Web Site Administration Tool
To access the Web Site Administration Tool, on the Website menu, click ASP.Net Configuration.
The following sections provide some considerations for working with the Web Site Administration Tool.
Restarting the Application When Saving
Most changes to configuration settings that you make in the Web Site Administration Tool take effect immediately. This requires the Web site to which the change applies to be restarted. Because this will cause currently active sessions in the Web site to be lost, you should make configuration changes to a staged or development version of the Web site before publishing these changes to the production server.
Saving Your Settings
Most changes to configuration settings that you make in the Web Site Administration Tool take effect immediately. For settings for which the Web Site Administration Tool interface has a dedicated Save button, leaving the Web Site Administration Tool idle or allowing the Web Site Administration Tool to time out before you click Save will cause your configuration settings changes to be lost.
As a security measure, the Web Site Administration Tool times out after a period of inactivity. Any settings that did not take effect immediately and were not saved will be lost. If the Web Site Administration Tool has timed out, close your browser, and then reopen the Web Site Administration Tool in a new window.
The Web Site Administration Tool manages only some of the configuration settings that are available to the Web site. Many other settings require direct modification of configuration files either manually, by using the, or programmatically, by using the .