[jira] [Commented] (LOG4NET-411) Release 1.2.13.0 is no longer compatible with .Net 2.0

2016-12-18 Thread Stefan Bodewig (JIRA)

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

Stefan Bodewig commented on LOG4NET-411:


If you use the official binaries downloaded from Apache and use the assembly 
from the net-2.0 directory then it is supposed to work on .NET 2.0 - as well as 
any assembly you've compiled yourself from sources.

> 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)


[jira] [Commented] (LOG4NET-411) Release 1.2.13.0 is no longer compatible with .Net 2.0

2016-12-16 Thread Jasneet (JIRA)

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

Jasneet commented on LOG4NET-411:
-

Does Log4Net version 1.2.13.0 support logging of .NET 2.0 applications? Please 
confirm.

> 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.3.4#6332)


[jira] [Commented] (LOG4NET-411) Release 1.2.13.0 is no longer compatible with .Net 2.0

2013-11-28 Thread Stefan Bodewig (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4NET-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13834637#comment-13834637
 ] 

Stefan Bodewig commented on LOG4NET-411:


The 3.5 CP assembly is not compatible with .NET 2.0, use the 2.0 assembly when 
targeting 2.0 - ist there any problem with 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)