NET Binding Redirects – Updating Referenced Assemblies Without Recompi(ferventcoder.com)

submitted by ferventcoderferventcoder(836) 2 years, 6 months ago

Have you ever seen this error? System.IO.FileLoadException: Could not load file or assembly ‘nameOfAssembly’, Version=specificVersion, Culture=neutral, PublicKeyToken=publicKey’ or one of it's dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) This means you’ve replaced the specific version of the third party assembly with either an earlier or an updated version. The assembly that uses it is compiled to point to a specific version of the assembly and now will not load. I’ve seen this the most with applications that use log4net and/or NHibernate and third party assemblies that also use log4net and/or NHibernate.

1 comment |category: |Views: 5

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
Comments:

posted by ferventcoderferventcoder(836) 2 years, 6 months ago 0

Had to fix the link when adding the DNK badge to the story ;( - http://www.dotnetkicks.com/csharp/NET_Binding_Redirects_Updating_Referenced_Assemblies_Without_Recomp

Reply

information Login or create an account to comment on this story