įollowing is part of the web.config file.
To turn this feature off, remove the registry value. Note: There is some performance penalty associated with assembly bind failure logging. To enable assembly bind failure logging, set the registry value (DWORD) to 1. WRN: Assembly binding logging is turned OFF. Information regarding the origin and location of the exception can be identified using the exception stack trace below.Īssembly Load Trace: The following information can be helpful to determine why the assembly ', Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded. (Exception from HRESULT: 0x80131040)Īn unhandled exception was generated during the execution of the current web request. The located assembly's manifest definition does not match the assembly reference. Please review the stack trace for more information about the error and where it originated in the code.Įxception Details: System.IO.FileLoadException: Could not load file or assembly ', Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. (Exception from HRESULT: 0x80131040)ĭescription: An unhandled exception occurred during the execution of the current web request.
What can cause the issue?Ĭould not load file or assembly ', Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. However, I got the following error after published it to azure website. I created a web project and it runs well in Visual Studio. Hi Selvakumar, I followed your steps and it crash me with log4net.dll: Could not load file or assembly ‘log4net’ or one of its dependencies., and log4net is not included in my web.config.