unloading assemblies after loading into AppDomain

Topics: CAB & Smart Client Software Factory
Jun 24, 2006 at 12:49 AM
originally posted by: Ashith

I heard a podcasts about CAB on ddj, where the speaker mentioned that it is not possible to unload the assembly once loaded.

My thoughts on this, can't we do this by loading the required assembly in a separate process and do some kind of a Interprocess communication.
Also, I came across a concept by Don Box called, passivation. in which The runtime allows workflows to be removed from memory (a technique called passivation) and later reloaded and resumed without making developers write explicit state management logic.

Can the above concept be utilised in CAB.
Jun 24, 2006 at 2:27 AM
originally posted by: PauloMorgado

You don't need another process. You just need another AppDomain. But you'll have a problem with the UI which needs to run in only one thread, so the assembly needs to be loaded in the AppDomain where the thread is running.

As for the workflow, I think the passivation is all about save the state (data) of the objects, not it's definition (class/type).