administrator permission are recommended for running visual studio sp1 on windows 7 rc

Question

I get this annoying message everytime I try to run visual studio 2005(even using "Run as Administrator" gives same message). I have VS 2005 Professional with all the latest service packs installed including vs2005 SP1 and vs 2005 update for Vista.

I am part of the administrators group on my machine. Still I have this problem.

Some read on the web suggests that Running program in Compatibility mode solves the problem. Others also recommend turning off the message forever.

Well my question is how do I turn off this warning which seems to bother me even if I am part of administrators group. Does Visual Studio does not run in administrator mode even when I am an administrator or even I use "Run as adminsitrator".

Also it would be greate if someone out there can highlight what features of Visual Studio wont be available if Visual Studio is launched as a normal user (User is not an administrator/part of the administrator group) on Windows 7.

Answer 1

As per my knowledge, If you have UAC on, then by default, VSStudio will launch with std users right, even if the logged-in user is an admin. You will need to run it as "Run As Administrator" to run it with full privileges. or run in built in Administrator's account.

If you run with std user's token, you will not be able to attach to applications that run with elevated permissions (ex. services) & processes running in someone else's account 9not very clear on this).

Also you will not be able to debug applications that need elevated privileges in the logged in account.

One solution is to make a short cut of VSStudio with run as administrator selected (via compatibility tab in properties of the shortcut). The other is turn off the warning & elevate only when required (recommended). Third is turn of UAC (worst option).

Answer 2

I just solved a similar problem when using VS 2008 on XP Professional

Navigate to the devenv.exe file, right click and select properties.

Most likely the account under which you have logged in will be selected and the permissions will not include "Full Access". Click Full Access and then click OK.

This worked for me.