London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
Hello,
We are currently looking into upgrading an Episerver solution using CMS 9.x and Community 7.5 to CMS 11.x and Community 9.
We've been following the steps mentioned in here but are experiencing an issue on start-up with the Log4Net versions required by several of the Episerver components.
As it stands I've been able to get Community to work together with CMS 11 - but at the cost of breaking the error logging by completely removing the EPiServer.Logging.Log4Net package. I'm unable to use assembly binding redirects to work around this due to the public key change - as such the only way I can see around this issue would be for EPiServer.CommonFramework to possibly be updated to no longer be dependant upon Log4Net 1.2.10 through NHibernate by either updating or removing the NHibernate dependency.
Has anyone experienced a similar issue / found a work-around?