This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

■

Note

If you debug this project (via F5), you will find many additional assemblies are loaded into each

AppDomain which are used by the Visual Studio debugging process. Running this project (via Ctrl + F5) will

display only the assemblies directly by each app domain.

Programmatically Unloading AppDomains

It is important to point out that the CLR does not permit unloading individual .NET assemblies.

However, using the AppDomain.Unload() method, you are able to selectively unload a given applica-

tion domain from its hosting process. When you do so, the application domain will unload each

assembly in turn.

Recall that the AppDomain type defines a small set of events, one of which is DomainUnload. This

event is fired when a (nondefault) AppDomain is unloaded from the containing process. Another

event of interest is the ProcessExit event, which is fired when the default application domain is

unloaded from the process (which obviously entails the termination of the process itself ). Thus, if

you wish to programmatically unload anotherAD from the AppDomainManipulator.exe process and be

notified when the associated application domain is torn down, you are able to write the following

event logic:

static void Main(string[] args)

{

...