Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Application domains are usually created and manipulated programmatically by runtime hosts. However, sometimes an application program might also want to work with application domains. For example, an application program could unload an application component into a ___domain to avoid having to stop the entire application.
The AppDomain class is the programmatic interface to application domains. This class includes methods to create and unload domains, to create instances of types in domains, and to unload domains. The following table lists commonly used AppDomain methods.
| AppDomain Method | Description |
|---|---|
| CreateDomain | Creates a new application ___domain. CreateDomain takes a set of properties that customize various aspects of the ___domain, such as the application base, or root directory for the application; the ___location of the configuration file for the ___domain; and the search path that the common language runtime is to use to load assemblies into the ___domain. |
| CreateInstanceFrom | Creates an instance of a specified type in the application ___domain. |
| Load | Loads an assembly into the application ___domain. |
| Unload | Performs a graceful shutdown of the ___domain. The application ___domain is not unloaded until all threads running in the ___domain have either stopped or are no longer in the ___domain. |
The unmanaged interfaces described in the common language runtime Hosting Interfaces Specification also provide access to application domains. Runtime hosts can use interfaces from unmanaged code to create and gain access to the application domains within a process.