Products
Packages [expand] [collapse]
Services
Released in version
2.2.2
2.2.1
2.1.0

Release notes for Episerver updates

This overview lists changes included in Episerver updates delivered as NuGet packages and services. Use the information to decide which updates to apply to your project, see Installing Episerver updates. Select a product, package, or service in the left menu, and filter for dates, features, or bug fixes.

  • See only new features (all features) - filter on item type Feature.
  • See only end-user (user interface) features - filter on item type UI Feature.
  • See only critical bug fixes - filter on item type Critical Bug.

Note: New NuGet packages listed here may not be immediately available in the Episerver NuGet feed.

Changes in EPiServer.Logging.Log4Net

Item type
From date
To date
Items/Page
Area Id Type Description Released
CMS-9761
  Log4Net logging stops working in Release mode

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/

Fix Version/s: EPiServer.Logging.Log4Net 2.2.2;
Feb 19, 2018
CMS-9555
  Initialization module using log4net directly disables 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.

Fix Version/s: EPiServer.Logging.Log4Net 2.2.1;
Feb 01, 2018
CMS-4327
  Log4Net provider CMS 10 compatibility

Updated version range to support EPiServer.Framework 10.0

Fix Version/s: EPiServer.Logging.Log4Net 2.1.0;
Oct 23, 2016