Re: VS2005/Vista issues

Tech-Archive recommends: Speed Up your PC by fixing your registry

It appears to work, and this is real blessing because I have to restart VS2005 SP1/Vista
about every 5 minutes these days (it crashes for no discernable reason, for example, doing
such unbelievably complex tasks such as reloading a file that changed outside the VS
editor, starting a compilation, breaking in the debugger, single-stepping, etc.). Thanks.
joe

On Mon, 18 Jun 2007 23:16:14 -0700, "David Ching" <dc@xxxxxxxxxxxxxxxxxxxxxx> wrote:

"Joseph M. Newcomer" <newcomer@xxxxxxxxxxxx> wrote in message
news:cage73tj26cvekaikuokodvhn3gkag6niq@xxxxxxxxxx
Which is exactly the rationale I'm applying. I don't want to deliver a
product that fails
in the field once deployed because it ran fine for me as admin, but won't
work for anyone
else.

What I want to do is twofold:
Never, ever have to explicitly run a program "as administrator" if I
always want
run it as administrator; double-clicking the icon will ask me if I want
to elevate, and I will click "continue" or "yes" or "ok" or whatever
is required
Never, ever have to supply a password in response to a privilege elevation
prompt


Right-click the shortcut (e.g. to DevEnv.exe) and click on Properties.
Click the Shortcut tab. Then click the Advanced button. Check "Run as
administrator." Now everytime you click the shortcut, it will elevate
automatically.

An Admin account doesn't prompt for a password to elevate.

If running in an Admin account is suspect, then create another account
called Limited and try your program there before delivering it. That's what
I do and it works great.

-- David

Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.

Quantcast