User Permissions and Visual Studio
Note
This article applies to Visual Studio 2015. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here
For reasons of security you should run Visual Studio as a normal user whenever possible.
Warning
You should also make sure not to compile, launch, or debug any Visual Studio solution that does not come from a trusted person or a trusted location.
You can do nearly everything in the Visual Studio IDE as a normal user, but, you need administrator permissions to complete the following tasks:
| Area | Task | For more information |
|---|---|---|
| Installation | Installing Visual Studio. | Installing Visual Studio 2015 |
| Upgrading from a trial edition of Visual Studio. | How to: Upgrade from a Trial Edition of Visual Studio | |
| Installing, updating, or removing local Help content. | Install and Manage Local Content | |
| Application types | Developing solutions for SharePoint 2010. | Requirements for Developing SharePoint Solutions |
| Acquiring a developer license for Windows Store. | Get a developer license (Windows Store apps) | |
| Toolbox | Adding classic COM controls to the Toolbox. | Using the Toolbox |
| Add-ins | Installing and using add-ins that were written by using classic COM in the IDE. | Creating Add-ins and Wizards |
| Building | Using post-build events that register a component. | Understanding Custom Build Steps and Build Events |
| Including a registration step when you build C++ projects. | Understanding Custom Build Steps and Build Events | |
| Debugging | Debugging applications that run with elevated permissions. | Debugger Settings and Preparation |
| Debugging applications that a run under a different user account, such as ASP.NET websites. | Debugging ASP.NET and AJAX Applications | |
| Debugging in Zone for XAML Browser Applications (XBAP). | WPF Host (PresentationHost.exe) | |
| Using the emulator to debug cloud service projects for Microsoft Azure. | Debugging a Cloud Service in Visual Studio | |
| Configuring a firewall for remote debugging. | Set Up the Remote Tools on the Device | |
| Performance tools | Profiling an application. | Beginners Guide to Performance Profiling |
| Deployment | Deploying a web application to Internet Information Services (IIS) on a local computer. | Deploying an ASP.NET Web Application to a Hosting Provider using Visual Studio or Visual Web Developer: Deploying to IIS as a Test Environment |
| Providing feedback to Microsoft | Changing how you participate in the Visual Studio Customer Experience Program. | How to: Send Feedback |
Running Visual Studio as an Administrator
You can launch Visual Studio with administrative permissions each time you start the IDE, or you can modify the application shortcut to always run with administrative permissions. For more information, see Windows Help.
To run Visual Studio with administrative permissions on Windows 8, Windows 8.1, Windows Server 2012, or Windows Server 2012 R2
On the Start screen, type Visual Studio. You should see the version or versions of Visual Studio you have installed.
Select the version of Visual Studio you want to start, and then bring up the shortcut menu (it appears at the bottom of the screen). Choose Run as administrator.
When Visual Studio starts, (Administrator) appears after the product name in the title bar.
To run Visual Studio with administrative permissions on Windows 7 or Windows Server 2008 R2
On the Start menu, choose All Programs.
In the Microsoft Visual Studio Version folder select Visual Studio Version open the shortcut menu, and then choose Run as administrator.
When Visual Studio starts, (Administrator) appears after the product name in the title bar.
See Also
Porting, Migrating, and Upgrading Visual Studio Projects Installing Visual Studio 2015