> I am working in a shop that uses VSS and we have a custom class library that is used by multiple programmers. This creates conflicts when one programmer has it checked out to work on one class in the library and another programmer is needing to access the library to modify a different class. Does anyone know a good scheme for handling this situation ?

Mike --

Another possibility is maintaining a temporary class library for each developer. To check out a class, check out the class lib. Launch 2 instances of the Class Browser and move the class from the main library to the temp library. References to parent classes are maintained in this process.

Larry's advice, in general, is also good. It may be possible to design your class libraries by the roles in your development group to minimize the need for workarounds.

Jay