> Hi, this is pretty much the same problem as I had :)
>
> Our solution is as follows (and comes straight from one of
> the Ms solution development centre (SDC) who we had in for
> consultancy on precisely this problem so I guess they use it too):
>
> * System Solution containing all projects - used for daily
> (overnight) builds
> * Subsystem Solutions containing _project_ references to all
> projects required by the subsystem
> * [1]In each subsystem solution have a debug build that only
> builds the projects in that subsystem and doesn't rebuild the
> referenced system.
> * In each subsystem solution have a NUnit build that only
> builds the project files required for the unit tests and runs
> the tests.
> * Strict design rules about which subsystem can reference another.
> * A coffee machine that takes 1/2 hour to make 1 cup of
> coffee for when you really do have to build everything ;)
Sounds nice, but don't you have a problem with sourcesafe then?
As the sourcesafe info is stored in a solution, and my experience is
that when you have a project added to multiple solutions, the real
sourcesafe nightmare begins... (but perhaps you solved it in a way,
don't know)
FB
===================================
This list is hosted by DevelopMentorŪ http://www.develop.com
Some .NET courses you may be interested in:
Essential .NET: building applications and components with CSharp
August 30 - September 3, in Los Angeles
http://www.develop.com/courses/edotnet
View archives and manage your subscription(s) at http://discuss.develop.com
