[ACCEPTED]-How to configure Visual Studio not to give UAC prompt on each run?-uac
Administrative Tools -> Local Security 4 Policy -> Local Policies -> Security Options 3 -> User Account Control: Behavior of the 2 elevation prompt for administrators in Admin 1 Approval Mode = Elevate without prompting.
VS 2005 was a pain in Vista, and there's 3 a lot of little gotchas even when running 2 as administrator. See if you can upgrade 1 to 2008, which works a lot better on Vista.
I've had to turn UAC off for my 2008 dev 20 system also, despite similar feelings about 19 wanting to be able to use it. It's just 18 too painful to need to keep track of the 17 running context of every single application 16 in order for things like drag/drop between 15 windows to work, or interacting with remote 14 systems, or debugging scenarios, or any 13 number of other tasks. UAC was a good idea 12 in theory, but there seems to have been 11 so little effort put in to making it functionally 10 useful for real-world power users, that 9 at the end of the day, the only feasible 8 solution is to disable it entirely.
Windows 7 7 will purportedly be somewhat better with 6 eliminating the constant prompts, but unless 5 they really work to address all the cross-application 4 and remote access issues, it's still going 3 to be a non-starter for anyone other than 2 novice users. Here's to hoping they eventually 1 get it to be actually usable.
Unfortunately UAC prompt is mandatory in 12 windows Vista, when UAC is enabled.
One 11 solution that worked for me is to have a 10 elevated command line and a bunch of non-ui 9 shell scripts that run elevated from there 8 for some tasks.
Also to debug I've setup 7 another computer in which I can run a remote 6 debugging session, it is a bit tricky to 5 configure with VS 2005, the plus is that 4 if you crash/hang the remote session it 3 didn't crash your main computer :)
PD: VS 2 2008 is slightly nicer in vista than VS 1 2005 give it a try if you can.
As far as I'm aware, you can't get everything 15 you want (UAC on, VS working without prompts).
However, there's 14 a better workaround than "have someone else 13 test it with LUA:" A Virtual PC. Use Virtual 12 PC (free from Microsoft) to create a guest 11 operating system. Install Vista and set 10 up a regular user as well as your default 9 admin. Test your apps on that VPC using 8 the regular (non-elevated) user. This at 7 least gives you the early indication of 6 LUA issues without too many major headaches.
I 5 agree that it's a bit of a pain (and I've 4 noticed VS2008 doesn't bug me with UAC prompts 3 under Vista nor Win7 beta), but it is what 2 it is. VS2005, particularly in debugging, requires 1 elevation to attach to processes, etc.
For the record, my current "solution" to 10 this problem, after a few days of experimenting 9 with it, is:
- turn UAC off
- make sure somebody else tests the application with a Standard User Acount on a regular basis
... i.e. use the same pattern 8 which worked in WindowsXP before.
I would 7 like to see some other solution, but so 6 far nothing I have tried gave me all of 5 what I want, i,e. UAC on, Visual Studio 4 working and no prompt on running VS. I would 3 like to keep UAC on, but it was too annoying 2 for me to confirm the elevation every time 1 I run the tools.
Norton has an interesting tool to de-tune 9 UAC and make it a little easier to live 8 with...at the cost of feedback about what 7 programs you run going to Norton. There 6 is a good write-up about it here:
The download 5 is here:
Finally, there is an interesting 4 little tool to "snooze" UAC which 3 costs $5 (30 Day trial). I can't vouch 2 for either tool as I have not tried them 1 personally.
More Related questions