3.0.0-preview.1
Issue for preparing the first preview of 3.0.0
Breaking Changes
Framework Support
Attention: Starting with 3.0.0 we only support the following target frameworks
- net462
- netstandard2.0
The reasoning for this change can be found in #111
Deleted obsolete API (#125)
- obsolete since 1.2.14 - 2015
-
log4net.Appender.BufferingAppenderSkeleton.OnlyFixPartialEventDataandlog4net.Appender.MemoryAppender.OnlyFixPartialEventData(you will need to change your config files fromonlyFixPartialEventData value="true"tofix value="Partial") -
log4net.Appender.ColoredConsoleAppender.ctor(ILayout) -
log4net.Appender.ColoredConsoleAppender.ctor(ILayout, bool) -
log4net.Appender.ConsoleAppender.ctor(ILayout) -
log4net.Appender.ConsoleAppender.ctor(ILayout, bool) -
log4net.Appender.DebugAppender.ctor(ILayout) -
log4net.Appender.EventLogAppender.ctor(ILayout) -
log4net.Appender.FileAppender.ctor(ILayout, string) -
log4net.Appender.FileAppender.ctor(ILayout, string, bool) -
log4net.Appender.SmtpAppender.LocationInfo -
log4net.Appender.TextWriterAppender.ctor(ILayout, Stream) -
log4net.Appender.TextWriterAppender.ctor(ILayout, TextWriter) -
log4net.Appender.TraceAppender.ctor(ILayout) -
log4net.Config.DOMConfigurator -
log4net.Config.AliasDomainAttribute -
log4net.Config.DomainAttribute -
log4net.Config.DOMConfiguratorAttribute -
log4net.Core.LoggerManager.GetLoggerRepository -
log4net.Core.LoggerManager.CreateDomain -
log4net.Core.LoggingEventData.TimeStamp -
log4net.Core.LoggingEvent.GetExceptionStrRep -
log4net.Core.LoggingEvent.FixVolatileData -
log4net.LogManager.GetLoggerRepository -
log4net.LogManager.CreateDomain
-
- obsolete since 2.0.6 - 2016
-
log4net.Util.SystemInfo.ProcessStartTime
-
-
log4net.Appender.RemotingAppender(see #154 - Remove RemotingAppender) -
log4net.Appender.NetSendAppender(see #158 - NetSendAppender removed) - dropped support for legacy serialization for .netstandard (see #174 and #175)
Other changes (#124)
-
log4net.Config.AliasRepositoryAttributeis now sealed -
log4net.Config.RepositoryAttributeis now sealed -
log4net.Config.XmlConfiguratorAttributeis now sealed - interface
log4net.Appender.AppenderCollection.IAppenderCollectionEnumeratoris now obsolete and must be replaced byIEnumerator<IAppender> -
log4net.Appender.MemoryAppender.m_eventsList(protected field) was changed fromArrayListtoList<LoggingEvent>- for getting
m_eventsList.SyncRootyou need to cast it:((ICollection)m_eventsList).SyncRoot
- for getting
-
log4net.Repository.Hierarchy.Hierarchy.EmittedNoAppenderWarningis now internal (see #157)
Bugs
- Regression: Creating nested loggers in reverse order fails in 3.0.0-preview.1 (#156 by @FreeAndNil)
- System.NullReferenceException when comparing with a null Level (#169 by @FreeAndNil)
- ColoredConsoleAppender writes UTF-8 preamble to the console on initialization (#168 reported by @RoboBurned, fixed by @FreeAndNil)
Enhancements
- #111 (by @fluffynuts and @freeandnil)
- #124 (by @erikmav)
- #125 (by @erikmav)
- #127 (by @freeandnil)
- #109 (by @mobilebilly)
@erikmav Can you test 3.0.0-preview.2 on your side?
Preview.1 and preview.2 both checked out on 2 services I run. Thanks for publishing - looking forward to the final release.
From: Jan Friedrich @.> Sent: Monday, July 29, 2024 2:08 AM To: apache/logging-log4net @.> Cc: Mention @.>; Subscribed @.> Subject: Re: [apache/logging-log4net] 3.0.0-preview.2 (Issue #139)
@erikmavhttps://github.com/erikmav Can you test 3.0.0-preview.2 on your side?
— Reply to this email directly, view it on GitHubhttps://github.com/apache/logging-log4net/issues/139#issuecomment-2255400834 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAHYCQQ6A7SLUJJNOKL4U7TZOYBCTBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLLDTOVRGUZLDORPXI6LQMWWES43TOVSUG33NNVSW45FGORXXA2LDOOJIFJDUPFYGLKTSMVYG643JORXXE6NFOZQWY5LFVA4DSNBUHA4DINECUR2HS4DFUVUXG43VMWSXMYLMOVS2UMRSGI2DSMRTGA4TTJ3UOJUWOZ3FOKTGG4TFMF2GK. You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.