[
https://issues.apache.org/jira/browse/LOG4NET-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834702#comment-13834702
]
Stefan Bodewig commented on LOG4NET-411:
----------------------------------------
Yes, the change was intentional in order to fix LOG4NET-404.
As long as you use the 2.0 version when you need to support 2.0 things should
work.
> 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)