>What approaches do you suggest for doing team development where all developers can create classes in a common class library. We have tried to use Visual SourceSafe to manage the conflicts between developers but to no avail. Visual SourceSafe only lets one person check out the class library at a time.
What we do is have our class libraries in one folder (or project as VSS classifies it). These class libraries are then shared with every project we work on. The main thing we do in regards to classes is that nobody adds, modifies or deletes classes from any libraries unless agreed upon by main development staff. Obviously, this is a procedural thing as opposed to a VSS function. I believe is VSS Admin though you can set a file to allow checkouts by more than one person however, personally I don't recommend this. HTH
Colin Magee
Team Leader, Systems Development
Metroland Media Group Ltd.
Mississauga, Ontario, Canada
cmagee@metroland.comNever mistake having a career with having a life.