How to persist an AppDomain and manually unload assembly? about appdomaintoolkit HOT 3 CLOSED

Yes, it will. So long as you call Dispose() on the context you can use it as long as you like. If you're using proxy objects, remember to handle their leases properly else the domain will GC it: http://msdn.microsoft.com/en-us/magazine/cc300474.aspx.

Closing a context will destroy the app domain--which in effect will also "unload" your assembly. Note that no actual unloading is ocurring--it's impossible to unload an assembly once loaded--instead we're tossing the domain away that contained the assembly. You have to be very, very careful here to not pollute the main domain with any classes from the remotely loaded domain--there are a couple of ways you can do this on accident. Mostly you should avoid reflecting across any classes inside the remotely loaded assembly outside of simple metadata queries, and be sure to only interact with that domain through serialized objects or proxies (those objects extending MarshalByRef)

from appdomaintoolkit.

Thank you for that.

from appdomaintoolkit.

No problem. Feel free to ask anything :). I need to add some unit tests demonstrating the above behavior (isolated assembly loading inside a context). Shouldn't be too hard to do--I'll make a note of it.

from appdomaintoolkit.