It’s unfortunately all too often recently that I’ve need to redirect assemblies, so I thought I’d write a quick post on the subject.<\/p>\n
Occasionally you may have a situation where one library (let’s call it Lib1) you’re using in .NET relies on a specific version of a another, strong-named, library (let’s call it Lib2). Then you go and update the library Lib2 to a newer version and things break. Lib1 expects a specific version of Lib2 and we’re not supplying it.<\/p>\n
Simple open\/add your App.config file – we then add something like this<\/p>\n
\r\n<runtime>\r\n <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">\r\n <dependentAssembly>\r\n <assemblyIdentity name="Lib2" publicKeyToken="Lib2-PublicToken" culture="neutral" \/>\r\n <bindingRedirect oldVersion="0.0.0.0-1.0.0.0" newVersion="2.0.0.0" \/>\r\n <\/dependentAssembly>\r\n <\/assemblyBinding>\r\n<\/runtime>\r\n<\/pre>\nObviously you replace Lib2 with the assembly that your code is dependent upon, you’ll also need to supply the publicKeyToken. The oldVersion is a range of versions from 0.0.0.0 to 1.0.0.0 in this case, meaning anything that required this assembly version 0 to 1 should now use version 2 (2.0.0.0).<\/p>\n
When adding further assembly redirects we of just supply further dependentAssembly elements.<\/p>\n
To find the publicKeyToken we can use the Strong Name utility (sn.exe) which can be found here (for example) <\/p>\n
\r\n"%ProgramFiles%\\\\Microsoft SDKs\\Windows\\v8.0A\\bin\\NETFX 4.0 Tools\\sn.exe" -T <assemblyName>\r\n<\/pre>\nWe can also find such information via the likes of ILSpy, by clicking on the assembly and in the right hand pane we’ll have information such as<\/p>\n
\r\n\/\/ Microsoft.VisualC, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a\r\n<\/pre>\nFurther Reading<\/strong><\/p>\n
Strong-Named Assemblies<\/a>
\nRedirecting Assembly Versions<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"It’s unfortunately all too often recently that I’ve need to redirect assemblies, so I thought I’d write a quick post on the subject. Occasionally you may have a situation where one library (let’s call it Lib1) you’re using in .NET relies on a specific version of a another, strong-named, library (let’s call it Lib2). Then […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[49],"tags":[],"class_list":["post-3421","post","type-post","status-publish","format-standard","hentry","category-net"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/3421","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/comments?post=3421"}],"version-history":[{"count":5,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/3421\/revisions"}],"predecessor-version":[{"id":9556,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/3421\/revisions\/9556"}],"wp:attachment":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/media?parent=3421"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/categories?post=3421"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/tags?post=3421"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}