Running Visual Studio without admin rights

visual-studio admin-rights
Sean Kearon picture Sean Kearon · Sep 28, 2010 · Viewed 23.3k times · Source

We work on XP Pro workstations and use Visual Studio 2008 & 2010 to develop winforms, web and web services against local IIS and SQL Express instances.

We currently have local admin rights on our main machine account. The proposal is to move to a low rights account for our amin login but to have another local account with local admin rights that we then use to elevate where needed.

Are there any issues developing and debugging under this setup that would affect developer productivity?

Answer

Paul Hadfield picture Paul Hadfield · Sep 28, 2010

From experience you can't install things like NUnit in your reduced priviledge account - that shouldn't be a problem for you as you can just type in the details of your higher priviledged account (it was a problem for us as we didn't have that). Also you'll need to do a similar thing if you're firing up services / IIS, etc. Again as you have it to hand it shouldn't be a problem.

My conclusion was that you could develop as a non-admin as long as you know the admin password - but if you don't know the admin password, you are going to be in for a very frustrating time!

Related questions

Why am I getting "Cannot Connect to Server - A network-related or instance-specific error"?

I get the following error when trying to connect to SQL Server: Cannot connect to 108.163.224.173. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the …

Read More
How do you auto format code in Visual Studio?

I know Visual Studio can auto format to make my methods and loops indented properly, but I cannot find the setting.

Read More
How do I remedy "The breakpoint will not currently be hit. No symbols have been loaded for this document." warning?

A C# desktop application on the express edition worked, but then it didn't work 5 seconds later. I tried the following: Ensure debug configuration, debug flag, and full debug information are set on all assemblies. Delete all bin and obj folders …

Read More