Run as Administrator message for VS 2005

[Guest]

Hi,

I'm getting the "Run as Administrator" message when I'm trying to run VS
2005 (the message that suggests to run VS with administrator permissions).

Now, I set VS 2005 to run with the admin permissions but the message keep
popping up!

The situation is described here:
http://www.ureader.com/message/33270881.aspx
(exactly the same case as mine, Vista Business with VS 2005 SP1)
and the answer he got is to turn off the uac.

I prefer to not turn off the uac, is there a better solution??
The message shouldn't pop up since I AM running with administrator
permissions.

Thanks,
Roee.

 

[Mr. Arnold]

Hi,

I'm getting the "Run as Administrator" message when I'm trying to run VS
2005 (the message that suggests to run VS with administrator permissions).

Now, I set VS 2005 to run with the admin permissions but the message keep
popping up!

The situation is described here:
http://www.ureader.com/message/33270881.aspx
(exactly the same case as mine, Vista Business with VS 2005 SP1)
and the answer he got is to turn off the uac.

I prefer to not turn off the uac, is there a better solution??
The message shouldn't pop up since I AM running with administrator
permissions.

That's the way it is. Anytime you set that Run as Administrator and the
program needs its privileges escalated, you're going to get some kind of
confirmation message. Even with you running as Admin with admin rights, the
Admin user rights are locked down in Vista and doesn't have full rights
like on previous versions of the NT based O/S such as XP Win 2K, etc, and if
you have to escalate privileges, a confirmation message may pop.

Are you aware of this, which may have to be applied to a .Net application so
that it can run on Vista with the proper privileges when it is deployed to a
Vista machine?

And truing off UAC may cause some other application that is or can be
installed on the machine that uses UAC to fail.

http://channel9.msdn.com/Showpost.aspx?postid=211271

And you may want to read this as well as it talks about UAC and several
other things.
http://blogs.zdnet.com/Ou/?p=785

 

[Guest]

Thanks Mr. Arnold.

The thing is, the message does not sound like it reminds me that I'm using
escalated privilidges, but tells me that I'm not, and I should.

"Administrator permissions are recommended for running Visual Studio 2005 SP1

Some tasks and scenarios will not work without Administrator permissions. We
recommend that you use 'Run as administrator' ..."

OK, so I want to follow the instructions and run VS 2005 as administrator,
how do I do that? I already checked the 'Run as administrator' checkbox in
the devenv.exe file properties and I'm not sure if I am with admin permission
or not, since I keep getting that message.

Thanks,
Roee.

 

[Mr. Arnold]

Thanks Mr. Arnold.

The thing is, the message does not sound like it reminds me that I'm using
escalated privilidges, but tells me that I'm not, and I should.

"Administrator permissions are recommended for running Visual Studio 2005
SP1

Some tasks and scenarios will not work without Administrator permissions.
We
recommend that you use 'Run as administrator' ..."

OK, so I want to follow the instructions and run VS 2005 as administrator,
how do I do that? I already checked the 'Run as administrator' checkbox in
the devenv.exe file properties and I'm not sure if I am with admin
permission
or not, since I keep getting that message.

You check on Run As Admin on the short-cut permanently on the VS 2005
short-cut and you click (ok) when the message pops. Or you don't set-up Run
As Admin for the VS 2005 short-cut and don't have the privileges you need to
do some development work. Those are your choices as it stands to date with
Vista and UAC. Or disable UAC and you may face other problems.

You do it on the Command Prompt short-cut RAA, it's not going to ask for
confirmation when you user it. You do it on the IIS7 short-cut off of
Control/Admin/Tools, and you're going to get prompted when you use the
application, whether you are Admin or not.

Login as a Standard User and see what happens when you have to give a
password. ;-)

 

[Guest]

Yeah, well that's what I did, it's checked on the shortcut, but I still get
the message.
Actually it doesn't bother as an annoyance too much, it just makes me fill
that something is wrong, and that I don't really know under which privileges
I'm running.

Thanks for the help.

 

[Seth]

Disabiling the UAC is the #1 thing that you SHOULD DO!

Then how come Linux and Unix users have been managing with their equivalent
of UAC for years? Standard practice in those environments is to log on as a
standard user and use "sudo" to execute a single command or "su" to elevate
a terminal window for the life of the window.

That's exactly what I do with Windows Vista and UAC. Right click an app and
choose "Run as Administrator" is the equivalent of "sudo" and opening a CMD
window via "Run as Administrator" is the equivalent of "su".

Saying "Disabiling the UAC is the #1 thing that you SHOULD DO!" is the
mantra of the clueless.

 

[Gerry Hickman]

Hi,

Basically everything about that message in VS2005 is WRONG. I complained
to Microsoft at the release of SP1 (and Vista patch) about it. They did
nothing.

Firstly, Visual Studio should not be run with Admin rights. Secondly,
all this rubbish from Microsoft about running with "least privilege is a
bit of a joke if their own products can't even comply.

The real problem is that Vista didn't exist when VS2005 was released,
they didn't want to spend much time on SP1 because ORCAS was round the
corner, so the answer (as always from Microsoft) is "Run everything with
Admin rights". They then force people to run with Admin rights in order
to use parts of their website because things like MSDN subscriptions, WU
Catalogue and WGA need to install ActiveX controls. Microsoft are
deliberately putting their customers at risk by making them run with
Admin rights. Now that's clueless.

Any developer who is running VS with admin rights should give up,
because all end-user and line-of-business apps need to run WITHOUT admin
rights. The only exception would be someone who is writing a device
driver and they shouldn't be using Visual Studio for that anyway, they
should have a special login session with internet access blocked.

Anyone who runs with Admin rights and browses the internet with IE7 is
fool (with or without UAC).

 

[Mr. Arnold]

Hi,

Basically everything about that message in VS2005 is WRONG. I complained
to Microsoft at the release of SP1 (and Vista patch) about it. They did
nothing.

Why should MS listen to you?

Firstly, Visual Studio should not be run with Admin rights. Secondly, all
this rubbish from Microsoft about running with "least privilege is a bit
of a joke if their own products can't even comply.

Based on what?

The real problem is that Vista didn't exist when VS2005 was released, they
didn't want to spend much time on SP1 because ORCAS was round the corner,
so the answer (as always from Microsoft) is "Run everything with Admin
rights". They then force people to run with Admin rights in order to use
parts of their website because things like MSDN subscriptions, WU
Catalogue and WGA need to install ActiveX controls. Microsoft are
deliberately putting their customers at risk by making them run with Admin
rights. Now that's clueless.

What does this have to do with OP's post?

Any developer who is running VS with admin rights should give up, because
all end-user and line-of-business apps need to run WITHOUT admin rights.

Who says?

Anyone who runs with Admin rights and browses the internet with IE7 is
fool (with or without UAC).

What does this have to do with VS 2005 and UAC?

It looks like you have some issues. Should we get you some tissues?

 

[Guest]

Try running with XP compatibility

Hi,

Basically everything about that message in VS2005 is WRONG. I complained
to Microsoft at the release of SP1 (and Vista patch) about it. They did
nothing.

Firstly, Visual Studio should not be run with Admin rights. Secondly,
all this rubbish from Microsoft about running with "least privilege is a
bit of a joke if their own products can't even comply.

The real problem is that Vista didn't exist when VS2005 was released,
they didn't want to spend much time on SP1 because ORCAS was round the
corner, so the answer (as always from Microsoft) is "Run everything with
Admin rights". They then force people to run with Admin rights in order
to use parts of their website because things like MSDN subscriptions, WU
Catalogue and WGA need to install ActiveX controls. Microsoft are
deliberately putting their customers at risk by making them run with
Admin rights. Now that's clueless.

Any developer who is running VS with admin rights should give up,
because all end-user and line-of-business apps need to run WITHOUT admin
rights. The only exception would be someone who is writing a device
driver and they shouldn't be using Visual Studio for that anyway, they
should have a special login session with internet access blocked.

Anyone who runs with Admin rights and browses the internet with IE7 is
fool (with or without UAC).

 

[Guest]

Even if you are an Administrator user on Vista you may have to "elevate
privileges" to use or modify some files and folders. I'm not sure whether
checking Run As Administrator on the program's shortcut is the same as
checking it on the actual program.exe file. You can set Vista to Run As
Administrator with elevated privileges on startup. Details in this tutorial.

http://www.vistax64.com/tutorials/80938-user-account-control-uac-elevate-privilege-level.html