Hi Srdjan
>
>I have been folowing this thread for a while now and I really could not understand why wld someone come up, or use solution that you are
>'more then proposing' here. Then in one of unrelated threads about source control you pretty much explained yourself.
>
>Keeping classes in separate classlibs DOES make sense if you were badly
>burned by downsides of using VSS or whatever else that u use. Number of VSS conflicts and related problems is realy downsized to minimum.
>But other then that, I see no other practical value to this aproach.
>
>I remember period of using VSS back in 1998 as simply - nightmare.
>Then we dropped it all together, and went back to solution where everybody had copy of full source on their local drives and master copy on (backed up) network drive.
>
>That is how we got our creative lifes back together :)
>

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!

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.