But which of the assemblies referenced in my project are suspects? How to check all the referenced assemblies of references assemblies? It’s task nobody would like to perform manually. Ok, there is a conflict between incompatible versions of log4net assembly. Choosing "log4net, Version=1.2.13.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a" arbitrarily. Then I checked the build log and found this line No way to resolve conflict between "log4net, Version=1.2.13.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a" and "log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304". The system cannot find the file specified.}}įirst I checked the bin directory and the assembly was not there. Solution: Open IIS Go to current server > Application Pools Select the application pool your 32-bit application will run under Click Advanced setting or. The system cannot find the file specified. > System.IO.FileNotFoundException : Could not load file or assembly 'log4net, Version=1.2.11.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a' or one of its dependencies. Could not load file or assembly log4net, Version1.2.10.0, Cultureneutral, PublicKeyToken692fbea5521e1304 or one of its dependencies. What was was worse and strange was the reason why they were failing System.TypeInitializationException : The type initializer for '' threw an exception. In one of my test projects the tests suddenly started to fail.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |