Instead of collecting classes into libraries based on their class (such as all forms together, all buttons together, etc), I've started building libraries based on the idea of a unit of work.

So, I might have (do have) one library with one specialized textbox class that get's subclassed for a number of different functions (different classlibs).

I don't honestly know how this would affect sourcesafe issues. :-\ But, I didn't like having the situation of wanting one form from a library of forms and getting the baggage of the whole library. Where I saw this was working on existing projects and have several classlibs each with many classes and not knowing which were really used or not.

>Hi Erik,
>Just out of curiousity ... how, logically, do you like to group your classes? I realize that this is a very subjective thing, and different people have different ways/reasons for grouping classes together into one vcx. I just wondered what your personal ideology was ...