DISQUS

DISQUS Hello! Huddled Masses is using DISQUS, a powerful comment system, to manage its comments. Learn more.

Community Page

Huddled Masses

Joel Bennett's development blog...
Jump to original thread »
Author

Installing a clean Development box

Started by Jaykul · 9 months ago

The hard drive in my development box died last week, and although I’ll spare you the story of the replacement process, I thought it might be interesting to document the process of rebuilding my dev box, and provide color commentary while I’m at it.


I ... Continue reading »

2 comments

  • Hi Joel,

    I've got to say no to "Add my domain account as an administrator."

    On both XP and Vista for the last two years we have had a basic domain account called "LocalAdmin" added as a local administrator to all dev workstations. We use this to install stuff. Otherwise, our personal domain accounts are just boring users (not even Power Users).

    Visual Studio, SQL Server, web development and all the usual stuff works fine as non-admin.

    Regards,
  • More power to you, I guess, if you're able to work without being in the administrators group.

    <notextile>

    Microsoft recommends that when using Visual Studio 2005, you do the following:

    <ul><li>Run Visual Studio with elevated administrator permissions</li><li>Be a member of the "Administrators" group on the local machine</li><li>Right-click the Visual Studio icon and select the "Run as administrator" option from the context menu</li></ul>
    </notextile>

    If you look at "this list of known issues":http://msdn2.microsoft.com/en-us/vstudio/aa972193.aspx which *only* apply to those using Visual Studio 2005 on Vista _without_ being an administrator, I find that several of those affect me. Just the process of "debugging web apps in IE":http://msdn2.microsoft.com/en-us/vstudio/aa972193.aspx#question16 is quite simply unacceptable, even leaving aside all the other problems, like the fact that _no_ profilers will work without being elevated, and you can't even browse web services on your own machine, and the managed code SDK debugger fails or hangs when a user changes options without elevated administrator permissions...

    Honestly, you'd have to be logging in as that administrative user each time you wanted to test an installer, or shut off or turn on the local SQL Server (which I don't leave running all the time).

Add New Comment

Returning? Login