BUG: You cannot administer the Web permissions for an ASP.NET Web application in the stand-alone version of Visual C# .NET or Visual C# 2005 (836735)
The information in this article applies to:
- Microsoft Visual C# .NET (2003)
- Microsoft Visual C# .NET (2002)
- Microsoft Visual C# 2005, Express Edition
SYMPTOMSIn the stand-alone version of Microsoft Visual C# .NET or Microsoft Visual C# 2005, you
cannot administer the Web permissions for an ASP.NET Web application.
Note This behavior occurs even if you specify FrontPage Extensions as the preferred access method to your Web server.WORKAROUNDTo work around this behavior, use the Internet Information
Services administration snap-in to administer the Web permissions for your
ASP.NET Web application. To do this, follow these steps:
- Click Start, click
Run, type
inetmgr in the Open box, and then click OK.
- If you are using Microsoft Windows 2000 or Microsoft Windows XP, the Internet
Information Services window appears.
- If you are using Microsoft
Windows Server 2003, the Internet Information Services (IIS)
Manager window appears.
- Administer the Web permissions for your ASP.NET Web
application:
- If you are using Windows 2000 or Windows XP, follow these
steps:
- In the left pane of the Internet Information
Services window, locate and then right-click the virtual directory
that contains your ASP.NET Web application.
- Point to All Tasks, click
Permissions Wizard, and then click Next.
You can now use the
Permissions Wizard to administer the Web permissions for your ASP.NET Web
application.
- If you are using Windows Server 2003, follow these steps:
- In the left pane of the Internet Information
Services (IIS) Manager window, locate and then right-click the virtual
directory that contains your ASP.NET Web application.
- Click Permissions. The
ApplicationPath dialog box appears, where ApplicationPath is a placeholder for
the path of your ASP.NET Web application.
You can use this dialog box to administer the Web permissions for your ASP.NET
Web application.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.REFERENCESFor more information, visit the following Microsoft Web
sites:
Modification Type: | Major | Last Reviewed: | 1/19/2006 |
---|
Keywords: | kbweb kbbug KB836735 kbAudDeveloper |
---|
|