[
https://issues.apache.org/jira/browse/LOG4NET-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834689#comment-13834689
]
Jørn Frode Jensen commented on LOG4NET-411:
-------------------------------------------
I see this has changed recently.
The page http://logging.apache.org/log4net/release/framework-support has
recently changed.
Google cache is helpful here.
*Microsoft .NET Framework 3.5*
??As of log4net 1.2.11 this version is identical to the .NET 2.0 version.??
This information is no longer there, so I can only guess that this was intended.
But it is definitely a breaking change.
Btw, I needed the .Net 2.0 support because I have a .Net 2.0 based application
that is used during upgrade of systems without .Net 4.
This application used some common components, and those can no longer log with
log4net during upgrade.
Probably an uncommon usecase, and I can live without it.
> Release 1.2.13.0 is no longer compatible with .Net 2.0
> ------------------------------------------------------
>
> Key: LOG4NET-411
> URL: https://issues.apache.org/jira/browse/LOG4NET-411
> Project: Log4net
> Issue Type: Bug
> Components: Builds
> Affects Versions: 1.2.13
> Reporter: Jørn Frode Jensen
> Labels: build
>
> According to Reflector output for the 3.5 client profile version of log4net,
> there is a reference from log4net.dll to System.Core version 3.5.
> Version 1.2.12.0 worked with .Net 2.0, but failed on dynamic methods
> ([LOG4NET-393]). This was fixed in 1.2.13.0, but this version now fails with
> .Net 2.0.
> Is this as designed?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
