.net - Is there a disadvantage in too much granularity in structuring projects? -


i have many classes in bll. supposed have itembll, itemtype bll, employeebll etc., there disadvantage in placing them in separate project each? of them logically groupable there problem in placing each class in separate project (lets maintaining them isn't problem).

how benefits of grouping them?

complexity biggest problem. more assemblies have, more have keep track of. if application needs one, there possibility need have reference others anyway if inner connected.

this isn't having more assemblies bad. there can advantages having them separate, such ones loaded memory when (they loaded on demand when application needs them).

there no hard , fast rule 1 better, depends on situation. personally, unless have reason have them separate, combine them. makes deployment , administration easier in long run. keeping classes in same assembly (at least in c# internal modifier), gives ability give them ability access functions internal assembly while blocking reference classes external it.


Comments

Popular posts from this blog

java - Run spring boot application error: Cannot instantiate interface org.springframework.context.ApplicationListener -

reactjs - React router and this.props.children - how to pass state to this.props.children -

Excel VBA "Microsoft Windows Common Controls 6.0 (SP6)" Location Changes -