Are you using Source Control? If you use Source Control, you can have a
whole slew of projects in your solution, and each developer keeps his/her
project(s) checked out, to prevent other developers from changing it. Using
the Configuration Manager prevents any projects the developer doesn't want
built from being built when debugging. And you can still step through code
in the other Projects.

Signature
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
You can lead a fish to a bicycle,
but it takes a very long time,
and the bicycle has to *want* to change.
> On my current project we work on basically 1 big intranet site that is
> made up of about 20 or so projects.
[quoted text clipped - 19 lines]
>
> Is there any guidance out there on this issue?
cmay - 15 Dec 2005 19:51 GMT
Kevin,
First off, sorry about the multiple posts... google had some error
pages when I was posting, guess it was in fact going through.
Anyway, yes we are using VSS, and I am familar with the technique you
describe.
The new TFS feature of "shelving" would make this methodology work even
better IMO.
Is this (using project references) the "best practice" as far as MS is
concerned?
Kevin Spencer - 15 Dec 2005 22:19 GMT
I haven't had the opportunity yet to work with TFS, but I'm looking forward
to it. Just waiting for the release of the Team System first. As for using
Project references, well, we've been doing that for so long I couldn't tell
you how we came across it. You can always check out the Microsoft Best
Practices site and see what you can find there:
http://msdn.microsoft.com/practices/

Signature
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
You can lead a fish to a bicycle,
but it takes a very long time,
and the bicycle has to *want* to change.
> Kevin,
>
[quoted text clipped - 9 lines]
> Is this (using project references) the "best practice" as far as MS is
> concerned?