Re: Best desktop OS for VS 2005

2. Never put VS2005 on a Windows Server 2003; this is completely and
utterly stupid and breaks every rule of client/server computing.

"this is ... stupid" - good argument. I think the last time I used that
argument was when I was about 19.

"breaks every rule of client/server computing" - Um. What? Visual Studio is
not a client/server application. And we're not talking about using a server
computer. We're talking about putting a server OS on a development computer.

We still use Win2000 client for VS2005 as it's superior to XP in every way

ROFLMOD.

our developers run with user rights, NOT admin rights. You should NEVER
run with admin rights.

Considering that previous remark about the superiority of Windows 2000 over
Windows XP, I'm not surprised. Perhaps we shoud revise that statement to
read "*I* should NEVER run with admin rights." I could go along with that.

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? BTW, what does this have to do with what OS one uses for
development?

If your Server 2003 is a production server it should be set up by an
expert from scratch as a custom build.

Again, nobody said anything about doing development work on "a production
server." I recommended installing Windows 2003 Server on a development
machine. Somehow I get the feeling that you don't know the difference
between a production server and a server OS. One is hardware. One is
software. They do not always share the same machine.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Show me your certification without works,
and I'll show my certification
*by* my works.

"Gerry Hickman" <gerry666uk@xxxxxxxxxxx> wrote in message
news:O%23LkfKEWGHA.4212@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

Comments related to original post

1. I agree with Windows 2000 it was very neat with the client/server
consistency. Same version of IIS and exact same DLLs for debugging.
Unfortunately, this is not damaged forever by Microsoft's new mismatched
o/s strategy.

2. Never put VS2005 on a Windows Server 2003; this is completely and
utterly stupid and breaks every rule of client/server computing.

3. Client o/s Win2000/XP/Vista?

We still use Win2000 client for VS2005 as it's superior to XP in every
way, but there will soon be things that will only work on XP or Vista so
it's worth getting ready for the slow and bloated "home user" experience
of a lifetime. We target Server 2003 with IIS6. I'm not aware of any
security issues; our developers run with user rights, NOT admin rights.
You should NEVER run with admin rights.

If your Server 2003 is a production server it should be set up by an
expert from scratch as a custom build.

lf wrote:
Kevin,

Thanks for your quick response. So, is it safe to assume that all the
potential security issues that we could encounter are not insurmountable
for a development environment? "Kevin Spencer" wrote:

Windows Server 2003 will be a great deal more difficult to set up due to
the increased security. However, if you're doing a web application, I
agree that it would be better to develop on the Windows Server 2003
platform, as your app will have to deal with these security issues as
well. As for IIS 6.0, it will be better for the app when deployed, but
not much different at design time.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Show me your certification without works,
and I'll show my certification
*by* my works.

"lf" <lf@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4AE47428-95AC-4AF0-8ABB-DA2CBBD6823C@xxxxxxxxxxxxxxxx
Not sure if this is the right group for this question, but it's kind a
hybrid, so here goes. Our production environment is moving to Windows
2003.
Presently, we have Windows 2000 server in production and all developers
desktops have Windows 2000 as well. This works well because we can on
our
desktops using the same environment as production. Now, we are moving
to
Windows 2003 on production and developers will be using Visual Studio
2005.
My question is this: What is the best OS for a developer. I have heard
that
people have had issues with Windows 2003 server on the desktop, so this
would
lead me to believe we should use XP Pro. However, I think XP Pro has
IIS 5.0
and Windows 2003 has IIS 6.0. Ideally, it would be great if developers
could
have the same level of IIS as production. What are other people using?
Since most of our applications are web applications it seems important
to
have the same version of iis on our development machines. Thanks in
advance
for your help.




--
Gerry Hickman (London UK)


.

Relevant Pages

  • Re: Getting management to move from green screen
    ... It's been in production use for over 2 years and works quite well. ... is installed on the client and executed. ... I've got a server side subroutine (Rule Module in D3 ... sniffer for windows clients or a passive RS-232 tap for "real" terminals. ...
    (comp.databases.pick)
  • Re: Switching from Mac to PC questions
    ... We're the production department of a weekly newspaper, ... We've been instructed to make switch from Quark 4.1 ... > Recently I switched to Windows and it ... > server consider Linux, but you might need a Windows server if ...
    (comp.publish.prepress)
  • Re: what Ports are used to map a remote drive
    ... arriving in production from a specific IP can access exposed resources. ... have mapped drive to a specific server in production. ... that only allows the specific ports to be opened from a specific IP ... Any Windows 2000pro or XPpro or 2K/2K3 server can accept a VPN. ...
    (microsoft.public.win2000.networking)
  • RE: 404 Not Found
    ... \par Welcome to MSDN newsgroup. ... \par From your description, you've a client/server based applications, the server is an ASP.NET webservice, currently you found that the server will always spend long time searching for some certain components, yes? ... Microsoft CDO for Windows 2000 ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: NET Framework 2.0 SP1/3.0 SP1/3.5 compatibility with WSS 3.0/MOSS 2007 SP1
    ... I would if running on Windows 2003 Server stick to .NET Framework 3.0 statement about that as far as I can remember. ... I need to know whether it's officially supported or not before I can do it in production. ...
    (microsoft.public.sharepoint.portalserver)