>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.

Colin's suggestions were good. In some cases, however, you'll need classes that are developed by one member of the team for their specific needs. We each have a library which cannot be changed by anyone else where we put containers, a specific class we are working on and adjusting frequently, etc. It's worked well with a 5-member team. Any team member can use another's library, but not change the classes.

Of course, base classes can only be changed by group agreement (or team-leader ruling if necessary :-) )

HTH