Question

I searched around but couldn’t find a solution for my dll issue.
My solution adds many dll references and each dll is strongly version dependent.
I just want to recompile one of them separately and add it back to the solution.
However, since other dlls are version dependent and reference this dll some
run-time errors happen saying the version is not the expected one.
How can I work around this situation?

Answer 1

Assembly redirection publisher policy entries in config file can solve that. Here is snippet of the sample from the article (you can also redirect ranges of versions too):

<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="myAssembly" 
          publicKeyToken="32ab4ba45e0a69a1" culture="en-us" />
        <bindingRedirect oldVersion="1.0.0.0" newVersion="2.0.0.0" />
        ....

Side note: you should consider your version policy more carefully. If you give assemblies to other people it may be better to avoid auto-generated version and use one version for each official release, potentially with minor versions for interim builds. Building all projects at the same time may be good idea to.