Working with web.config Files in Windows SharePoint Services
[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]
In a Microsoft Windows SharePoint Services deployment, web.config files are contained in the following folders within the file system:
Local_Drive:\Inetpub\wwwroot\wss\VirtualDirectories\*<guid>—*The web.config file that defines configuration settings for a SharePoint content application. In addition, the \wpresources folder contains a web.config file used in Web Part resources.
Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\wpresources—A web.config file that is used in Web Part resources for the global assembly cache.
Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG—The web.config file and other .config files that together define configuration settings for extending other virtual servers.
Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI—The web.config file that defines configuration settings for the /_vti_bin virtual directory.
Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS—The web.config file that defines configuration settings for the /_layouts virtual directory.
Local_Drive:\Inetpub\wwwroot\wss\VirtualDirectories\<guid>—The web.config file that defines configuration settings for the SharePoint Central Administration application.
When an IIS Web site is extended with Windows SharePoint Services, a top-level web.config file is placed within the content root folder of the Web application, which defines configuration settings for the server such as HTTP handling for Web Parts. Another web.config file used for Web Part resources is placed in a \wpresources folder within the same content root folder.
Important
The web.config files in the \wpresources folders should not be modified. The settings of these files disallow pages or items that can be compiled. If these settings are changed, the security state for the compiled code will be very different from the security state for code that runs from the Local_Drive:\Inetpub\wwwroot directory.
Typical customizations involving web.config files include such contexts as the following:
How to: Add Custom Configuration Settings for Extending Virtual Servers
How to: Modify Configuration Settings for an Application to Coexist with Windows SharePoint Services
Warning
Changes that you make to web.config may be overwritten when you install updates or service packs for Windows SharePoint Services, or when you upgrade an installation to the next product version.