Menu
What is the difference between using Visual Studio 2012 "Run as Administrator" mode and otherwise? Why do developers prefer using VS in administrator mode? What are the advantages/privileges that one gets? I may be naive enough to ask this one but I am just curious. Thanks.
934
Without Administrative permissions Visual Studio is not able to write to the hard drive outside of your specific user account privileges. This severely limits what can be done to build custom ArcGIS based applications.
Running apps as an administrator in Windows gives them extra privileges. It lets them edit the registry, change system files, and access other folders that are usually restricted. Sometimes, you need to run a program in administrator mode every time you use it.
You can use Run as to start an application as an administrator if you want to perform administrative tasks when you are logged on as a member of another group, such as the Users or Power Users group.
Although Microsoft recommends against running programs as an administrator and giving them high integrity access without a good reason, new data must be written to Program Files for an application to be installed which will always require admin access with UAC enabled, while software such as AutoHotkey scripts will ...
From MSDN: User Permissions and Visual Studio
You can do nearly everything in the Visual Studio IDE as a normal user, but, you need administrator permissions to complete the following tasks:
- Installing Visual Studio.
- Upgrading from a trial edition of Visual Studio.
- Installing, updating, or removing local Help content.
- Developing solutions for SharePoint 2010.
- Acquiring a developer license for Windows Store.
- Adding classic COM controls to the Toolbox.
- Installing and using add-ins that were written by using classic COM in the IDE.
- Using post-build events that register a component.
- Including a registration step when you build C++ projects.
- Debugging applications that run with elevated permissions.
- Debugging applications that a run under a different user account, such as ASP.NET websites.
- Debugging in Zone for XAML Browser Applications (XBAP).
- Using the emulator to debug cloud service projects for Windows Azure.
- Configuring a firewall for remote debugging.
- Profiling an application.
- Deploying a web application to Internet Information Services (IIS) on a local computer.
- Changing how you participate in the Visual Studio Customer Experience Program.
80
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
