c# - .NET compiled third-party DLL reference conflict -


I am using (a .NET CMS), and it is a reference to a DLL for a specific version ( See 1 humbra reference below). It's okay while I try to hook into the .NET MailChimp API, which gives a different type of reference to the same DLL (see 2 PerceptiveMCAPI below).

I can think of some options to solve it

a either obtain Umbraco or PerceptiveMCAPI source and reference the same version of DLL, in fact for compatibility reasons such Do not want to bump 2 DLL in b GAC, I want to avoid it because as soon as someone forgets, I look at the issues that arise (I know that we have automatic deployment Should, but time is restricted)

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

1 Umbreco Reference

  // Assembly Reference CookComputing.XmlRpcV2 Version: 2.4.0.0 Name: CookComputing.XmlRpcV2, version = 2.4.0.0 , Culture = neutral, public keynote = a7d6e17aa302004d  

2 PerceptiveMCAPI

/ / AssemblyPropiMCPI, Version 1.2.4.3 Location: C : \ WORK \ AEGPL \ AEGPL_VISITY \ BIN \ PERSPECTIVE MCPI DIELE NAME: PERSPECTIVIC MCPI, Version = 1.2.4.3, Culture = Neutral, PublicKey Tokens = Faucet Type: Leib Eri

The all is due to present GAC. I can think that only other alternative measures are to deliver these DLLs to sub-directories, so that CLR can not find them and implement epidomine. Exceptional Resolve Now you will keep that code updated for every new version.


Comments