Effect of Assembly size

Hi,

I have an application written in such a way that it support reflection based instantiation, and my question is, is it beneficial if I devide my code in to small set of libraries or have all code in to huge library.

some more specifics: Applicaiton is having multiple sub systems and each sub system has multiple modules and each module has 3+ tiers (UI,DAL,Data,BLL). If I keep library per module+tiers there would be too many libraries, so we are debating if we can merge all modules in to one huge subsystem library. That way we will have very few libraries to maintain, but I think that approach may have some issue, as when we instantiate one type from one module, whole library would be loaded in memory and that may un-necessarily load my application.

Is it true? Does any one have any good explanation of how would it affect if I merge all libraries in to one big library?

Thanks

[922 byte] By [Hiten] at [2007-12-26]

«« DataGridView and Calendar cells
»» Can you create sql statements by editing the *.xsd file?

# 1

In our experience, the size of the assembly hasn't had a noticable effect on the performance of creating types via reflection or using P/Invoke to execute the code. But if you have framework code that cycles (via reflection) through the types, methods, and custom attributes looking for things, that's where you might see a penalty. Consider caching up the metadata you need as you find it.

erikj at 2007-9-4 >

Architecture

Architecture General

Architecture Hot Topic

Architecture New Topic

Architecture

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech