Reading following on Dana's blog ! I think his argument is right! Even I also set VS2005 on vista to run with admin user because if I dint, I was not able to get the intellisense!! (Standard user is not allowed to re-write the NCB file - intellisense file!!) Lets wait and watch for Microsoft's response!!
Well, I installed SP1 of Visual Studio 2005 yesterday on my laptop running Vista, and I have to say there was one think that really disappointed me. So much so that I am not just going to blog about it... I want everyone that reads this to go AGAINST Microsoft recommendations. Here is what I mean:
Thats right.... Microsoft is recommended to run Visual Studio as Administrator. NO. NO. NO. NO. NO. Don't do this!!
You are on Vista. You should be running as a Standard User, and running Visual Studio as a standard user. Why? Because then you can SEE how your application will work while in least privilege mode AS you develop the software.
Now, some people will complain that they need to be administrator because they need some of the tools in the IDE. A good example would be if you are writing a COM component. You cannot register the library when running as a standard user. Is there a solution? Yes. Open up a cmd window as Administrator and do it by hand. Don't like that idea? Have a post build event that runs a custom app to do it... and modify the manifest to REQUIRE the UAC elevation. This way, you elevate a separate process to do your administrative task without requiring the IDE to be run with higher privileges that you really don't need.
And NOTHING prevents you from starting a second copy of VS2005SP1 elevated in those cases where you really have to debug as Administrator. But for your day to day use of VS... DON'T run elevated!!!
I am really surprised and disappointed to see this dialog. I only hope Microsoft reconsiders this position in its next version. If they REQUIRE admin privs for some tools, separate them out so only they have to be run as Administrator. You should only elevate when you need to; you should try to run with least privilege throughout the entire development process so you can REALLY see the impact of the code on normal users.
Well, IMNSHO anyways.
Source: Disappointment in VS2005 SP1 on Vista
Originally published on Wed, 27 Dec 2006 16:28:26 GMT by Dana Epp