Frameworks should be multiple DLLs, that have specific needs, not general. Can you imagine if the .Net framework was a single assembly?

I suggest a good reading of this book (also available online for free)

http://www.barnesandnoble.com/w/framework-design-guidelines-krzysztof-cwalina/1100508652?ean=9780321605009&itm=1&usri=framework+design+guidelines

>The framework contains over 100 classes for most of today's business needs in regards to application deployment. This is installed nationwide. Some clients need 1/3 of the classes while others will use 2/3 and so on. Depending on their needs, they might have only Framework.dll and TheNameOfTheClientWebSite.dll in the bin directory or, with that, some additional DLLs that specific classes, if the application needs them, are using.
>
>No, there is no relationship between PDF and ecommerce. Those are two separate classes. They have been mentioned as an example of classes that are in needs of a specific DLL. I have about 4 or 5 in total that are tied into the framework which are useful for some of its classes.