Re: two setup overview questions
From: Chris (Chris_at_discussions.microsoft.com)
Date: 01/16/05
- Next message: David Jessee: "Re: two setup overview questions"
- Previous message: Lee H: "RE: adding a blank entry into a combo box"
- In reply to: Scott Allen: "Re: two setup overview questions"
- Next in thread: Scott Allen: "Re: two setup overview questions"
- Reply: Scott Allen: "Re: two setup overview questions"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 16 Jan 2005 13:41:04 -0800
I read the articles that were linked in both responses, thank you.
I see the advantages with Source Save but if you,as a developer, are
required to have all the necessary componets and server on your local
workstation that can get pretty expensive and resource intense. I currently
use a P4, 2.8G, 1GDDR, etc. and can't see running IIS, SQL Server, Mail
server(if using non-CDONTS), all the third party com objects, etc.
I can see maybe IIS installed locally and have always hoped for a local
version, better than what was attempted before with Personal Web Server. Then
I guess you could 'bounce' all the other requests, i.e. Data, Mail, etc off
of a real server.
I still don't see the point though, if two developers happen to be working
on the same pages, in isollation, then move to the production web server, who
wins? Unless you 100% lock the files, then what about someone making changes
to the production server that effect others? I don't see a full-proof way of
doing it?
I personnelly like the workstation/server set-up, servers are servers and PC
are workstations. Maybe that's just old school.
"Scott Allen" wrote:
> Hi Chris:
>
> I belive option #1 is the most popular. It allows a dev to work and not interfere
> with other dev work on the team. Any laptop that can handle 512MB / 1GB of
> RAM should handle the setup just fine.
>
> Neither scenario favors source control management over the other. Any approach
> taken should include source control.
>
> Have you seen: Team Development with Visual Studio .NET and Visual SourceSafe
> [1]?
>
> [1] http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/tdlg_rm.asp
>
> --
> Scott
> http://www.OdeToCode.com/blogs/scott/
>
> > I would love to be pointed in the direction of resources that help
> > better understand the following (I've spent considerable time
> > searching the MS website):
> >
> > 1.) As a ASP.NET developer I've traditionally worked in the
> > environment of a workstation with VS.NET and a Windows2003 server with
> > IIS6.0 and SQL Server. Is that the most popular model. I know that if
> > a developer needed to travel that they could install IIS and Sql
> > Server locally, but the amount of resources needed to run all that
> > seems too great, especially if you have the hardware, network, etc in
> > a development studio.
> >
> > 2.) Does either one of these set-ups aid the use of Source Save? I
> > still like the approach of the separate server doing the server role.
> > That my client workstation has VS.NET, etc but no servers running.
> >
> > What is the Microsoft recommened set-up for both VS.NET and Visual
> > Source Save?
> >
> > Thanx.
> >
>
>
>
- Next message: David Jessee: "Re: two setup overview questions"
- Previous message: Lee H: "RE: adding a blank entry into a combo box"
- In reply to: Scott Allen: "Re: two setup overview questions"
- Next in thread: Scott Allen: "Re: two setup overview questions"
- Reply: Scott Allen: "Re: two setup overview questions"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
