Hi anthony,

I found that only reason to do so, is because of multi-developer projects where source control is used. However as David mentioned there are other ways to circumvent the problem. In fact I'm currently doing a project with 3 developers on the same project, where one is the lead developer and the other two are working on certain modules, where we use the strategy of synchronizing periodically.

IMO, The disadvantage of having one class per classlibray is that it clutters up the project manager which does not make it easier to find classes. If you group your classes logically into groups than it might be easier to quickly get at the class you need. For example, I've got a classlib that handles the integration of Crystal Reports into my projects. It only contains classes directly related to Crystal Reports. Another library contains the personal framework. A third one will contain reusable project depended classes. The 4th the project dialogs and forms.

Also, a large number of classlibraries will make your executable significantly larger, since the whole VCX/VCT is copied into your exe including tableheader etc. It will add approx 1.7 Kb to your exe for each and every classlib. In my case it would increase the filesize about 10 - 15%.

For the rest, it might be just a personal preference of style of programming.

Walter,