logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominik Psenner (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (LOG4NET-411) Release 1.2.13.0 is no longer compatible with .Net 2.0
Date Fri, 16 Dec 2016 15:04:58 GMT

     [ https://issues.apache.org/jira/browse/LOG4NET-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dominik Psenner closed LOG4NET-411.
-----------------------------------
    Resolution: Invalid
      Assignee: Dominik Psenner

Thanks for bringing up this issue, I'm closing it as invalid.

As for your question, you'll have to evaluate for yourself if log4net works for your usecase.
To find that out, more investigation has to be done than finding an answer for the question
"is .net framework 2.0 supported?".

> 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
>            Assignee: Dominik Psenner
>              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.3.4#6332)

Mime
View raw message