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

I don't want to further spread this discussion, as I could pretty much agree
with arguments placed here before by David / Walter.

I don't know, maybe using particular framework requires different
aproaches, but if you are happy with what you do, that is simply great.

To each it's own.

Rgds++
Sergio










>
>We know not to build a single record with multiple sets of data in it because of conflicts. If I build a record (package) with patient information, drugs and billing information, I will have potential conflicts from admitting, nursing and billing. We normalize to have a patient record, a drug history table and a billing history table.
>
>Like goes with like. Unlike is separated.
>
>I can see having multiple classes in one classlib ONLY when the set of classes are so intertwined as to be a single class. But then, ideally there should not be any such classes or modules or procedures or functions.