.NET compiled third-party DLL link conflict

Question

I use Umbraco (.NET CMS) and refers to a specific version of the DLL (see 1 Umbraco). This is normal until I try to connect to the .NET MailChimp API, which references a different version of the same DLL (see below 2 PerceptiveMCAPI).

I can come up with a couple of solutions to this problem.

but. Get either the Umbraco source or PerceptiveMCAPI and refer to the same version of the DLL, really do not want to do this for compatibility reasons.

b. Dump 2 DLLs in the GAC, I want to avoid this, because I see deployment problems that arise if someone forgets (I know that we must have automatic deployment, but time is limited)

I remember that there is a third option to indicate which version of the DLL to use in the configuration. Is this possible and what code is for it?

1 Umbraco Link

// Assembly Reference CookComputing.XmlRpcV2 Version: 2.4.0.0 Name: CookComputing.XmlRpcV2, Version=2.4.0.0, Culture=neutral, PublicKeyToken=a7d6e17aa302004d 

2 PerceptiveMCAPI

 // Assembly PerceptiveMCAPI, Version 1.2.4.3 Location: C:\Work\AEGPL\AEGPL_Website\bin\PerceptiveMCAPI.dll Name: PerceptiveMCAPI, Version=1.2.4.3, Culture=neutral, PublicKeyToken=null Type: Library 

Answer 1

It is for this reason that the GAC exists. The only other workaround I can think of is to populate these DLLs in subdirectories so that the CLR cannot find them and implement AppDomain.AssemblyResolve. Now you can save this code for each update of the new version.