Mutli-Developer Environment

[Brad Aurisch]

All help greatly appreciated: We have a team of ~20
people. We're based in ASP development, growing into .NET
work.

Our ASP development model is to have a central server
that everyone attached to via FrontPage extensions.
FrontPage managed the vss integration for us, everyone
had their own copy of a the project that simply pointed
at this central webserver. Under this model you can see
the effects of everyone's work straight away, you can
build dependencies on this work without having that code
articulated in your project definition. If you needed to
review or modify this code doing a project refresh would
discover all of the new elements and allow you to review.

What is the multi-developer env solution for .NET? So far
we've come up each developer running a local environment
putting the project definition in a common vss and each
of us using this common project definition, every time
you want to add a file to the project though you have to
acquire the project control in order to make the change.
Then everyone else needs to reload the project to acquire
all of the changes.

This model drastically slows our cycle time for change
down. Is there a better more elegant way? I'm guessing
(or perhaps hoping) msdn.microsoft.com isn't built in
such a crude multi-developer model.

Any guidance greatly appreciated.

b

[Eric Gunnerson [MS]]

Brad,

I suggest you ask this on http://www.asp.net. The asp.net team hangs out
there, and there are lots of good ASP programmers there as well.

--
Eric Gunnerson

Visit the C# product team at http://www.csharp.net
Eric's blog is at http://blogs.gotdotnet.com/ericgu/

This posting is provided "AS IS" with no warranties, and confers no rights.
"Brad Aurisch" <an*******@discussions.microsoft.com> wrote in message
news:83****************************@phx.gbl...

All help greatly appreciated: We have a team of ~20
people. We're based in ASP development, growing into .NET
work.

Our ASP development model is to have a central server
that everyone attached to via FrontPage extensions.
FrontPage managed the vss integration for us, everyone
had their own copy of a the project that simply pointed
at this central webserver. Under this model you can see
the effects of everyone's work straight away, you can
build dependencies on this work without having that code
articulated in your project definition. If you needed to
review or modify this code doing a project refresh would
discover all of the new elements and allow you to review.

What is the multi-developer env solution for .NET? So far
we've come up each developer running a local environment
putting the project definition in a common vss and each
of us using this common project definition, every time
you want to add a file to the project though you have to
acquire the project control in order to make the change.
Then everyone else needs to reload the project to acquire
all of the changes.

This model drastically slows our cycle time for change
down. Is there a better more elegant way? I'm guessing
(or perhaps hoping) msdn.microsoft.com isn't built in
such a crude multi-developer model.

Any guidance greatly appreciated.

b