Size of class libraries

[Razzie]

Hey all,

Does it matter what the size of your compiled class libraries is? Since I
started developing for my company, I keep adding new classes to my library
almost everyday (of course under different and neat namespaces). Is it ok to
place everything in one large dll file, or should I split it up? It's not
like I have 1000 classes or something though - the complete library has
around 25 classes now, though some are for completely different projects. Is
it wise to split them up for completely different projects (and thus
namespaces, getting something like Company.Project1.dll and
Company.Project2.dll)? I like the idea of having one complete library to
use, but what is the impact of this on peformance? Does the system simply
load only the classes from the dll it needs? Does it load the completely
library? I hope someone can give me some info on this.

Thanks a lot,

Razzie

 

[Marina]

I would say, that if the classes kind of logically fall into groups, where
each group is relevant to one project, that in that case you might want to
split it up into several projects/DLL's.