Several assemblies memory usage

[Steve B.]

Hi,

If I split my application into several assemblies instead of one
application, will it consume more memory ?

I actually have an application with an auto update mecanism. I split the app
into several assemblies in order to deploy only updated assemblies. However,
I'm not sure this is memory cost free to have many assemblies.

Thanks for any clarifications,
Steve

 

[tamberg]

If it does consume more memory the overhead is very low. We modularize
our applications extensively (more than 50 assemblies) without a
problem.

 

[Steve B.]

Thanks !

 

[Alex Yakhnin]

Remember,

That CF runtime will load the assembly into memory only when the method that
belongs to this assembly is called and then it would compile (JIT) the code
on the method by method basis, so from the memory usage point of view it is
better to have you app modularized.

-Alex

 

[Steve B.]

The app is supposed to be closed very rarely... (actually only at app
updates).
Will the CF finally release JIT result to frees memory ?

 

[Alex Yakhnin]

Will the CF finally release JIT result to frees memory ?

Yes, the JIT'ed code is also garbadge collected in CF. It is called code
pitching. See this post by Steve for details:
http://blogs.msdn.com/stevenpr/archive/2005/12/12/502978.aspx

-Alex

 

[Steve B.]

Thanks for this clarification.

Steve

Yes, the JIT'ed code is also garbadge collected in CF. It is called code
pitching. See this post by Steve for details:
http://blogs.msdn.com/stevenpr/archive/2005/12/12/502978.aspx

-Alex