>>It has nothing to do with VSS. Especially without VSS, two developers can be working on the same classlib. So when they both save a copy to the main set of code on the server, one of them looses out. That's insane!
>
>What exactly is insane ?
>
>Why wld they work on server if they hv workable LOCAL copy of all project sources with all comon class libraries databases etc ...
>
>It is just matter of having sound policies about submiting (overwriting) files on master copy. This could be either one apointed senior in a role of 'class librarian' , if team has young unexperenced members, or simply caution/torough testing if team is seasoned & well organized.
>

Someone should have the release code (final set of code used to produce the exe for release). A backup of the release code should be kept on the server. Having one person responsible for collecting the code reduces the team's productivity. It becomes a log jam. That's why source control products exist.

It is still possible for a change made by one developer to be lost by the librarian being human and making a mistake. All that has to happen is for the librarian to accept a file from developer B without merging it with the code from developer A. The librarian could also attempt to merge the code and still make a mistake.