I've also attempted to strongly type the new log4Net, e.g.:
LOG: Attempting download of new URL file:///E:/Websites/ MySite/WRN: Comparing the assembly name resulted in the mismatch: Revision NumberĮRR: Failed to complete setup of assembly (hr = 0x80131040). LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework/v7/Temporary ASP.NET Files/dev/bbf437a3/411124d9/log4net/log4net.DLL. LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework/v7/Temporary ASP.NET Files/dev/bbf437a3/411124d9/log4net.DLL. LOG: Post-policy reference: log4net, Version=1.4, Culture=neutral, PublicKeyToken=b32731d11ce58905 LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v7\config\nfig. LOG: Using application configuration file: E:\Websites\MySite\www\dev\web.config LOG: This bind starts in default load context. LOG: Initial PrivatePath = E:\Websites\ MySite\www\dev\bin
LOG: Appbase = file:///E:/Websites/MySite/www/dev/ LOG: DisplayName = log4net, Version=1.4, Culture=neutral, PublicKeyToken=b32731d11ce58905 Ironically, Log4Net dutifully records the attempt to bind to the obsolete version fo log4Net: See the inner exception for more details. The located assembly's manifest definition does not match the assembly reference. I see these errors logged on Azure (App Service) on every restart of the App Service: Main message: Startup assembly StartupBootstrapper failed to execute. Unfortunately, simply replacing the reference in my ASP.NET Bin directoryĬould not load file or assembly 'log4net, Version=1.4, Culture=neutral, PublicKeyToken=b32731d11ce58905' or one of its dependencies. The web app was originally built with v1.4.
I'm attempting to upgrade (at last!) the log4net install on my ASP.NET (II7, 64 bit, Windows 2008) web site to log4net v1.2.11.0.