Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We are working on a big portal that developed in SharePoint 2007 ..
We put custom code in Dlls .. some suggest to put all code for many components into one single dll instead of one dll for each component ..
My opinion is to put each component into a separate dll to affect memory in a good way ..
So, which is the better really .. to put all components into one single dll or have one dll for each component ?
You should create different assemblies for any reusable code. If you are not planning to reuse your code then its better to have the code in one assembly .. as it increases performance..
You should also check the following two threads
Does .NET assembly size affect performance?
.NET Cross-Assembly Performance Hit