Number of assemblies

  • Thread starter Thread starter Thore Berntsen
  • Start date Start date
T

Thore Berntsen

When I develop a .NET CF soulution I often end up with a rather large number
of assemblies, up 10 - 15. I try to put releated functionallity in one DLL.

I'm not sure if this is a good practice on a .NET CF soultion? Should it try
to limit the number of assemblies.

Any comments?

Thore
 
Managed assemblies don't have the virtual memory costs that native DLLs do,
so the number of assemblies doesn't matter.

-Chris
 
Hey Chris,

Further to this question, from a assembly loading point of view is it better
to have large assemblies or many small assemblies. Looking at this from the
aspect of initial load and discovery of referenced assemblies.

Looking on the pure performance numbers.

Mark
 
Chris, do I understand correctly that there is no 64 KB minimum size of
a loaded .NET DLL?
 
Correct because they are loaded differently than native DLLs. They are
memory mapped into shared memory space, so they don't take up 64k of your
processes virtual space.

-Chris
 
Back
Top