![]() ![]() NET 4, added it as a reference to my web application project, recompiled and then re-opened the user control and the error disappeared. I ended up just downloading the latest log4net.dll for. I did notice after building though that a log4net.dll was copied into my "bin" directory and I right clicked on it and figured out it was related to Apache Foundation. Ultimately, I was not able to figure out which of the third party DLLs was actually referencing log4net. We wanted to take advantage of the extra memory 64-bit will offer our IIS application pools. 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. My guess here is that we're compiling a DLL in 64-bit but its referencing a 32-bit dll? I would agree with what Matt Palmerlee said above - switching the application pool to 32-bit mode DOES FIX the problem but your still stuck in a 32-bit application pool. Could not load file or assembly 'log4net, Version1.2.10.0, Cultureneutral, PublicKeyToken692fbea5521e1304' or one of its dependencies. An attempt was made to load a program with an incorrect format. ![]() The located assembly's manifest definition does not match the assembly reference. The error I was receiving within our one of our user controls was the following: ASP.NET runtime error: Could not load file or assembly 'log4net' or one of its dependencies. Could not load file or assembly 'log4net, Version1.4, Cultureneutral, PublicKeyTokenb32731d11ce58905' or one of its dependencies. We had a similar issue with our web application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |