Export (0) Print
Expand All


Updated: August 22, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1

This feature is not available on Windows XP 64-Bit Edition and the 64-bit versions of the Windows Server™ 2003 family. For more information, see "Features unavailable on 64-bit versions of the Windows Server family" in Help and Support Center for Windows 2003.

Microsoft ASP.NET is more than just the next generation of Active Server Pages (ASP). It provides an entirely new programming model for creating network applications that take advantage of the Internet. This section includes information about configuration, security, and deployment of ASP.NET applications.

FrontPage Server Extensions does not support unicode content directory names or Web Distributed Authoring and Versioning (WebDAV). New FrontPage Server Extensions virtual servers should be assigned to the MSSharePointPool application pool. Also, do not make changes to the MSSharePointPool application pool configuration.

   If you have a Web site that uses Sharepoint™ Team Services (STS) from Microsoft, the following types of pages do not work without excluding the virtual directory containing the pages from the STS ISAPI filter:

  • ASP pages

  • ASP.NET pages

  • PHP pages

  • PerlScript pages


To enable these types of pages to work on your STS Web site
  1. In the Central Administration Web site for STS, choose to Manage your virtual directory or Web site.

  2. Under Defined Managed Paths, type the path to the virtual directory that contains your excluded pages (such as \MyASPPages) and select Exclude.

This section includes the following information:

Related Information

Community Additions

© 2016 Microsoft