4 ms·
One example of that I have run into at work is mismatched versions of json.net in dependencies. It becomes a mess when you realize one requires an older/newer v
by yareally 10y ago
One example of that I have run into at work is mismatched versions of json.net in dependencies. It becomes a mess when you realize one requires an older/newer version and you don't have the source to modify it or will take some time to have the developer of the dependency update their project.
- will_hughes 10y agoSo long as the newest version of the assembly is backwards compatible with the previous ones (i.e has same interfaces, etc) - then this is easily solved using Assembly binding redirection[1] in your .config file. eg I have JSON.NET 8.0 installed, and a library I'm requires an earlier version then this will do the trick: <dependentAssembly> <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-8.0.0.0" newVersion="8.0.0.0" /> </dependentAssembly> Nuget takes care of this for you automatically. [1] https://msdn.microsoft.com/en-us/library/eftw1fys(v=vs.110).aspx https://msdn.microsoft.com/en-us/library/eftw1fys(v=vs.110)....