I'll preface this by saying "I am not a programmer!"

That being said, I am having a programming issue. I have two third party modules that require CookComputing.XmlRpcV2.dll. The problem being, they require different versions of that DLL, but the filename remains the same. If I include the old version, module A breaks, if I include the new version, Module B breaks.

Error message: Could not load file or assembly 'CookComputing.XmlRpcV2, Version=2.4.0.0, Culture=neutral, PublicKeyToken=a7d6e17aa302004d' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

How can I have these two different DLL's coexist within DNN despite having the same file name -- WITHOUT writing any code (since they are 3rd party modules.)

If that question can't be answered, then... if I were to go back to one of the developers, how do I get them to fix this issue? Which developer should fix it (the developer referencing the older version)?

 3rd option

<configuration><!-- This is the opening tab in (my) web.config -->

<!-- I found that this needs to be at the end of the web.config, right above the closing configuration tag -->
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <probing privatePath="bin;bin\HttpModules;bin\Providers;bin\Modules;bin\Support;" />
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions" culture="neutral" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="3.5.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

For more information on using this, google assemblybinding and/or dependentassembly - those should give you enough to get it working