Re: Best desktop OS for VS 2005
- From: Gerry Hickman <gerry666uk@xxxxxxxxxxx>
- Date: Wed, 19 Apr 2006 22:41:41 +0100
Hi Kevin,
I guess I'll have to tell our network admin not to allow me to be a network admin any more. Of course, if he's out of town, who will fix the network when it goes down?
What I said was you should never "run" with Admin rights, if you have an Admin login and you are the backup guy then that's different. You would log in as Admin if there was an emergency, but that doesn't mean you are actually running as Admin all the time.
Again, nobody said anything about doing development work on "a production server." I recommended installing Windows 2003 Server on a development machine.
In my view this is a very bad idea, they'd also need a lot of licenses for Server 2003, e.g. a whole MSDN subscription for EVERY developer. They are also tied into this o/s instead of Vista on the client. They won't be getting used to how security tokens pass from client to server with this setup and won't be ready for how their app will perform on a real world situation.
--
Gerry Hickman (London UK)
.
- Follow-Ups:
- Re: Best desktop OS for VS 2005
- From: Kevin Spencer
- Re: Best desktop OS for VS 2005
- References:
- Re: Best desktop OS for VS 2005
- From: Kevin Spencer
- Re: Best desktop OS for VS 2005
- From: Gerry Hickman
- Re: Best desktop OS for VS 2005
- From: Kevin Spencer
- Re: Best desktop OS for VS 2005
- Prev by Date: Re: saving interim project versions
- Next by Date: Re: VS.NET 2003 - Error after Windows updates installed
- Previous by thread: Re: Best desktop OS for VS 2005
- Next by thread: Re: Best desktop OS for VS 2005
- Index(es):
Relevant Pages
|