The version of log4net should be configurable via assembly dependentAssembly section in web.config.
Add/modify this section in your web.config:
Hi Quan, I did try changing the dependentAssembly in web.config to
but NO luck.
Also found through Process Explorer, a few process using the old version 126.96.36.199 of log4net from GAC including Episerver.scheduler.svc and noticed these are running on .net framework 2.0.
Trying many things, finally we decided to use a separate config and log file for custom logs and another config and log file for internal logs . Which does what we need ! But still curious why is it still using old version of log4net in a few places.
On a side note I noticed the base Episerver folder has old 188.8.131.52 dlls which I replaced to new 184.108.40.206 that didnt help either.
Please share any thoughts or ideas you may have!
Thanks in advance!
Note that the publicKeyToken should be 1b44e1d426115821 instead of 669e0ddf0bb1aa2a. You might want to take a look here:
Unfortunately It didnt work in our case.
The issue was C:\EpiServer\eCommerceFramework\5.2\XavierCommerceManager\Sites\IntegrationService\bin had the old version of dll and replacing that with the new version solved the issue.
Thanks and appreciate your help Quan!
Episerver is not writing custom and internal logs together. It writes custom logs with the below code in Application_start event but not internal logs. Without the below code it writes internal logs but not custom logs. Its always either or
var logfile = new System.IO.FileInfo(HttpContext.Current.Server.MapPath("log4net.config"));
Also in the log4net trace I noticed its trying to load old version of log4net (220.127.116.11) though we upgraded to 18.104.22.168 version.
Where should I check the Episerver log4net versions? Or how can I find out where its using the older version ?