Visual Studio Run as administrator shortcut

Question

how do I create a shortcut that runs Visual Studio with Administrator rights?

Actually I have to navigate to the Visual Studio start menu folder, click on the icon with

Answer 1

I know the OP was about how to create a shortcut that runs VS as admin, but using the steps below you can just always have VS launch as admin.

This is a copy of my answer to a similar post on SuperUser:

Option 1 - Set VSLauncher.exe and DevEnv.exe to always run as admin

To have Visual Studio always run as admin when opening any .sln file:

1. Navigate to C:\Program Files (x86)\Common Files\Microsoft Shared\MSEnv\VSLauncher.exe.
2. Right-click on VSLauncher.exe and choose Troubleshoot compatibility.
3. Choose Troubleshoot program.
4. Check off The program requires additional permissions and hit Next.
5. Click the Test the program... button to launch VS.
6. Click Next, then hit Yes, save these settings for this program, and then the close buton.

To have Visual Studio always run as an admin when just opening visual studio directly, do the same thing to the DevEnv.exe file(s). These file are located at:

Visual Studio 2010

C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe

Visual Studio 2012

C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe

Visual Studio 2013

C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe

Visual Studio 2015

C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe

Option 2 - Use VSCommands extension for Visual Studio

Install the free VSCommands extension for Visual Studio (it's in the Visual Studio Extensions Gallery) and then configure it to always have Visual Studio start with admin privileges by going to Tools -> VSCommands -> Options -> IDE Enhancements -> General and check off Always start Visual Studio with elevated permissions and click the Save button.

Note: VSCommands is not currently available for VS 2015, but their site says they are working on updating it to support VS 2015.

My Opinion

I prefer Option 2 because:

• it also allows you to easily turn off this functionality.
• VSCommands comes with lots of other great features so I always have it installed anyways.
• it's just easier to do than option 1.