|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. ArchiveDisclaimer|
Using Visual Web Developer as a Non-Administrative User
Updated: April 2009
As a security best practice, it is recommended that you log on to your computer as a user that does not have administrative privileges. Running as a non-administrative user can help limit the effect of a security breach, because a process that runs in your non-administrative user context does not have unlimited access to resources.
You can run Visual Web Developer when you are logged on as a non-administrative user, but certain features are not available. In general, these are not limitations in Visual Web Developer itself but in other processes that Visual Web Developer interacts with. To avoid these issues, you can run Visual Web Developer as an administrator by right-clicking the application icon and selecting Run as Administrator from the context menu.
The following table lists features in Visual Web Developer that are not available if you are logged on as a non-administrative user.
Creating a new local or remote IIS Web site
You cannot make changes to the Internet Information Services (IIS) metabase (for example, creating new entries) because it requires administrative privileges. This affects your ability to configure some settings in the Web.config file.
Opening a local or remote IIS Web site
You cannot make changes to the IIS metabase (for example, creating new entries) because it requires administrative privileges. This affects your ability to configure some settings in the Web.config file.
You cannot run your Web site unless you use the ASP.NET Development Server, which is the default Web server for file-system Web sites. Alternatively, you can set project options to open the browser and point to the Web site using IIS. For details, see How to: Specify the Web Server for Web Sites.
Debugging a local or remote IIS Web site
You cannot attach to a process that is running under the IIS worker process because it requires administrative privileges.