<dependentAssembly> Element

  • Article

Encapsulates binding policy and assembly location for each assembly. Use one <dependentAssembly> element for each assembly.

<configuration>
   <runtime>
      <assemblyBinding>
         <dependentAssembly>

<dependentAssembly>
</dependentAssembly>

Child Elements

Element Description
<assemblyIdentity> Contains identifying information about the assembly. This element must be included in each <dependentAssembly> element.
<codeBase> Specifies where the runtime can find a shared assembly if it is not installed on the computer.
<bindingRedirect> Redirects one assembly version to another.
<publisherPolicy> Specifies whether the runtime applies publisher policy for this assembly.

Example

The following example shows how to encapsulate assembly information for two assemblies.

<configuration>
   <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
         <dependentAssembly>
            <assemblyIdentity name="myAssembly"
                              publicKeyToken="32ab4ba45e0a69a1"
                              culture="neutral" />
            <!--Redirection and codeBase policy for myAssembly.-->
         </dependentAssembly>
         <dependentAssembly>
            <assemblyIdentity name="mySecondAssembly"
                              publicKeyToken="32ab4ba45e0a69a1"
                              culture="neutral" />
            <!--Redirection and codeBase policy for mySecondAssembly.-->
         </dependentAssembly>
      </assemblyBinding>
   </runtime>
</configuration>

Configuration File

This element can be used in the application configuration file, machine configuration file (machine.config), and the publisher policy file.

See Also

Runtime Settings Schema | Configuration File Schema | Redirecting Assembly Versions