Ray6 wrote:
 |
jb43081 wrote:
Actually the best practice is to develop and test as a user, and only elevate your privlidge to Administrator as needed.
|
What?! You can do that?! Then what the hell is all the fuss about? Sorry, I was under the impression that VS tools hadn't been updated to allow for that? Is that not the case?
Actually, there is a "power toy" for XP that will let you do that. I haven't used it since I started using Vista, so the name escapes me, but I'll see if I can find it when I get home tonight. It basically allowed you to run your apps in a lower privlidge mode than your current one.
You couldn't debug in it, which makes sense when you consider just how intrusive things like debugging and profiling are (you are basically able to access system memory) so that made some permissions based issues a little more difficult to sniff out, but we would narrow it down, then throw a mess-o' logging around it.
Ray6 wrote:
 |
jb43081 wrote:
And to be hoenst, I think the level of frustration and intrusion over UAC are a bit exaggerated. The fact of the matter is that no matter what Microsoft does here (with security) there is always going to be someone who is unhappy.
|
Well, remember that the only people who are complaining are geeks, who spend a lot of time fiddling with their systems, and press hacks who are trying to attract hits from geeks. Haven't really heard from any of the normal folk out there.
True, and geeks probably already understand that what they are doing is potentially something that someone could exploit and know that they have to be patient. The news peope are the ones who aggrevate me; they act like normal Joe User would be unable to use Vista because it would be asking them to allow actions every five seconds. To be honest, even when I'm developing, unless I'm doing something I know is probably a security risk anyway, I don't get bugged by UAC enough for it to be a problem.