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.
While you frequently don’t want one monolithic assembly for anything more than a small project, it’s possible to separate things too much.
What are the signs/smells of too much assembly separation?
The first (obvious) one is: in a solution with lots of projects, assemblies with only a handful (say, 3-4) classes in them (an assembly with only interfaces may be an exception to this).
Another: If an assembly somewhere in the middle layer of your project has to import a ton of other assemblies in order to do its job.