Using application configuration files

You can use an application configuration file to direct the CLR to load a version of an assembly different than the one stored in the calling application's manifest.

This example shows how an application can direct the CLR to use Data Provider build 1.0.159 for an application built against any prior 1.0.x build of Data Provider:

 <configuration>
   <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
         <dependentAssembly>
            <assemblyIdentity name="Sybase.Data.AseClient"
                              publicKeyToken="26e0f1529304f4a7"
                              culture="neutral" />
            <bindingRedirect oldVersion="1.0.0.0-1.0.158.65535"
                             newVersion="1.0.159.0"/>
         </dependentAssembly>
      </assemblyBinding>
   </runtime>
</configuration>

Refer to the MSDN Library for complete configuration file schema information.