Release notes for Optimizely CMS and Customized Commerce updates

All log4net logging stops working when running in release mode. Only affects EPiServer.Logging.Log4Net v2.2.1

Workaround
Add the following AppSettings to the web.config.

<appSettings>
    <add key="log4net.Config" value="EPiServerLog.config"/>
    <add key="log4net.Config.Watch" value="True"/>
</appSettings>

Reported through
https://swapcode.wordpress.com/2018/02/16/no-logs-after-upgrading-episerver-logging/

1. Add the following intialization module:

   [InitializableModule]

   public class AA : IInitializableModule

   {

   private static readonly log4net.ILog _log = log4net.LogManager.GetLogger("test");

   public void Initialize(InitializationEngine context)

   {}

   public void Uninitialize(InitializationEngine context)

   {}

   }

EXPECTED: Logging works
ACTUAL: Logging stops working

Note: Sometimes for this bug fix to take affect you have to clear "Temporary ASP.NET Files", ie C:\Windows\Microsoft.Net\Framework64\v4.0.30319\Temporary ASP.NET Files\

WORKAROUND: An easy fix is to use namespace EPiServer.Logging.Compatiblity instead of log4net, to make sure log4net can be safely initialized from CMS instead from a custom initialization module.