Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4NET Dev" <log4net-dev@logging.apache.org>
Date: Thu, 28 Nov 2013 09:09:35 +0000 (UTC)
From: =?utf-8?Q?J=C3=B8rn_Frode_Jensen_=28JIRA=29?= <jira@apache.org>
To: log4net-dev@logging.apache.org
Message-ID: <JIRA.12681718.1385629662366.43034.1385629775067@arcas>
In-Reply-To: <JIRA.12681718.1385629662366@arcas>
References: <JIRA.12681718.1385629662366@arcas>
Subject: [jira] [Created] (LOG4NET-411) Release 1.2.13.0 is no longer
 compatible with .Net 2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

J=C3=B8rn Frode Jensen created LOG4NET-411:
-----------------------------------------

             Summary: 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=C3=B8rn Frode Jensen


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.=20

Version 1.2.12.0 worked with .Net 2.0, but failed on dynamic methods ([LOG4=
NET-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)