Most of you know that Sitecore CMS
Since earlier Sitecore versions (pre 6.3) rely on older versions of these 3rd party assemblies and most implementers are logically striving for using latest and greatest, conflicts of assembly versions arise. And strangely enough, I am hearing about these issues quite frequently now.
So how can these conflicts can be resolved?
Well, since an option of registering those in GAC is almost always a big NO-NO, the following technique proved to be workable for a few customers. It is called assembly version redirection.
What you need to do is add the following into the web.config’s <assemblyBinding>. The following example covers the “Newtonsoft.Json” assembly, however this is applicable to any other 3rd party assembly:
<dependentAssembly> <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" /> <codeBase version="220.127.116.11" href="C:\wwwroot\Sitecore\WebSite\new_bin\Newtonsoft.Json.dll"/> </dependentAssembly>
Afterwards, feel free to reference the newer version in your Visual Studio project, just remember to set the “Copy Local” property to False.
Note that since the release of Sitecore 6.3, most of those 3rd party assemblies were updated, so this article may be completely useless to you. Just make sure to check the exact Sitecore
As always, thanks goes to our tech support for finding such a plausible alternative.