AppDomain.DynamicDirectory Property


The .NET API Reference documentation has a new home. Visit the .NET API Browser on to see the new experience.

Gets the directory that the assembly resolver uses to probe for dynamically created assemblies.

Namespace:   System
Assembly:  mscorlib (in mscorlib.dll)

abstract DynamicDirectory : string with get
override DynamicDirectory : string with get

Property Value

Type: System.String

The directory that the assembly resolver uses to probe for dynamically created assemblies.

Exception Condition

The operation is attempted on an unloaded application domain.

To set the dynamic directory, assign a base directory path to the AppDomainSetup.DynamicBase property of the AppDomainSetup object that will be used to create the new application domain. The base directory path you assign to the property is modified by the addition of a subdirectory whose simple name is the hash code of the string you assign to the AppDomainSetup.ApplicationName property, so the format of the base directory is original path\hash code. The dynamic directory is a subdirectory of this base directory. Its simple name is the value of the AppDomainSetup.ApplicationName property, so its format is original path\hash code\application name.

The following example creates an application domain with a directory for dynamic assemblies, emits a dynamic assembly and stores it in the dynamic directory, and then loads the assembly into the new application domain and uses it.

The example creates an AppDomainSetup object and sets its ApplicationName property to "Example" and its DynamicBase property to "C:\DynamicAssemblyDir". The example then displays the DynamicBase property, to show that the hash code of the application name has been appended as a subdirectory of the path that was originally assigned.


The base directory in this example is intended to be outside the probing path for the example application. Be sure to compile the example in a different location. Delete the base directory and all its subdirectories each time you run the example.

The example creates a new application domain, using the AppDomainSetup object. The example uses the DynamicDirectory property to retrieve the name of the directory, so it can create the directory. (The example could just as easily create the directory beforehand by concatenating the original path, the hash code of the application name, and the application name.)

The example has a GenerateDynamicAssembly method that emits an assembly named DynamicHelloWorld.dll and stores it in the new application domain's dynamic directory. The dynamic assembly contains one type, HelloWorld, that has a static method (Shared method in Visual Basic) named HelloFromAD. Calling this method displays the name of the application domain.

The Example class derives from MarshalByRefObject, so the example can create an instance of the class in the new application domain and call its Test method. The Test method loads the dynamic assembly by its display name and calls the static HelloFromAD method.

You can show that the dynamic directory is searched after the normal probing paths by writing code for an assembly named DynamicHelloWorld.dll and compiling it in the same directory as this example. The assembly must have a class named HelloWorld with a static method named HelloFromAD. This method does not have to have the same functionality as the one in the example; it can simply display a string to the console. The assembly must also have an AssemblyVersionAttribute attribute that sets its version to When you run the example, the assembly you compiled in the current directory is found before the dynamic directory is searched.

No code example is currently available or this language may not be supported.


for access to the path information. Associated enumeration: FileIOPermissionAccess.PathDiscovery.

.NET Framework
Available since 1.1
Return to top