[jira] [Commented] (LOG4NET-556) Rolling file appender only recognises dates in yyyy-MM-dd format.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-556:


GitHub user Snotface opened a pull request:

https://github.com/apache/log4net/pull/43

LOG4NET-556 - Allow for dates that aren't necessarily in the -MM-dd 
format.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Snotface/log4net trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/log4net/pull/43.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #43


commit ee948d16ed620b6e2c77881c0ace528556c0bb0a
Author: Steven Nicholas 
Date:   2017-03-08T07:08:26Z

Allow for dates that aren't necessarily in the -MM-dd format.




> Rolling file appender only recognises dates in -MM-dd format.
> -
>
> Key: LOG4NET-556
> URL: https://issues.apache.org/jira/browse/LOG4NET-556
> Project: Log4net
>  Issue Type: Bug
>  Components: Appenders
>Affects Versions: 2.0.7
> Environment: Windows 7 and 10.
>Reporter: Steven Nicholas
>Priority: Minor
>  Labels: fix
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> Rolling file appender wouldn't recognise date format if it differed from 
> yyy-MM-dd in the config file and would roll to the next file for every logged 
> event, leading to thousands of files with the suffix MMdd-xxx.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user robcube commented on the issue:

https://github.com/apache/log4net/pull/16
  
Bingo, found the culprit:
```

  

```

Changed it to
` `

Problem solved. :-) I guess XmlLayoutSchemaLog4j isn't quite there yet.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user NachbarsLumpi commented on the issue:

https://github.com/apache/log4net/pull/16
  
I guess that writing xml tags that include a namespace results in the 
observed exception. Few people use xml layouts for logs, so this might be a 
regression or an incompatibility that shows itself only with .net core. Would 
you please create an issue for this so that we can track it better? I encourage 
you further to investigate in this.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user robcube commented on the issue:

https://github.com/apache/log4net/pull/16
  
Getting a weird error using .net core 1.1:
```
var logRepository = LogManager.GetRepository(Assembly.GetEntryAssembly());
XmlConfigurator.ConfigureAndWatch(logRepository, new 
FileInfo("log4net.config.xml"));
ILog Log = LogManager.GetLogger(typeof(Program));
Log.Debug("hey!");
```
at last line results in:
```
System.ArgumentException: Invalid name character in 'log4j:event'. The ':' 
character, hexadecimal value 0x0x3A, cannot be included in a name.
   at System.Xml.XmlWellFormedWriter.CheckNCName(String ncname)
   at System.Xml.XmlWellFormedWriter.WriteStartElement(String prefix, 
String localName, String ns)
   at log4net.Layout.XmlLayoutSchemaLog4j.FormatXml(XmlWriter writer, 
LoggingEvent loggingEvent)
   at log4net.Layout.XmlLayoutBase.Format(TextWriter writer, LoggingEvent 
loggingEvent)
   at log4net.Appender.FileAppender.Append(LoggingEvent loggingEvent)
   at log4net.Appender.AppenderSkeleton.DoAppend(LoggingEvent loggingEvent)
```



> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (LOG4NET-554) LogicalThreadContext was removed in .NETStandard

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-554:


GitHub user twcclegg opened a pull request:

https://github.com/apache/log4net/pull/42

LOG4NET-554 Use AsyncLocal for LogicalThreadContext

Replaces System.Runtime.Remoting.Messaging.CallContext which was removed in 
.NETStandard, with System.Threading.AsyncLocal which exists in .NET 4.6 and 
above

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/twcclegg/log4net-1 AsyncLocal4

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/log4net/pull/42.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #42


commit 53d435577890ef9a68b8929acead75301be9151a
Author: Thomas Clegg 
Date:   2017-02-27T20:37:50Z

LOG4NET-554 Use AsyncLocal for LogicalThreadContext

commit cdcf231b028db599ff9f04705dc9ca1a0ecb17a0
Author: Thomas Clegg 
Date:   2017-02-27T21:14:44Z

remove LogicalThreadContext from not supported list




> LogicalThreadContext was removed in .NETStandard
> 
>
> Key: LOG4NET-554
> URL: https://issues.apache.org/jira/browse/LOG4NET-554
> Project: Log4net
>  Issue Type: Bug
>  Components: Builds
>Affects Versions: 2.0.6, 2.0.7
> Environment: .NETStandard1.3
>Reporter: Thomas Clegg
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> LogicalThreadContext was excluded from dotnetcore version due to 
> System.Runtime.Remoting.Messaging no longer being available going forward.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (LOG4NET-550) Logging recursively from an Appender not supported for NET_4_0 and MONO_4_0

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-550:


GitHub user JJoe2 opened a pull request:

https://github.com/apache/log4net/pull/41

Recursive logging

Fixes LOG4NET-550

This fix will be needed to implement logging from the AsyncAppender I am 
working on.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/JJoe2/log4net RecursiveLogging

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/log4net/pull/41.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #41


commit ba250994011db8406b1965ff0bd71dfff7f5b771
Author: JJoe2 
Date:   2017-02-01T12:15:44Z

Unit test to show that recursive logging from an Appender fails 
(LockRecursionException thrown and swallowed by log4net core) if NET_4_0 or 
MONO_4_0 is defined.

commit 54048581c2ce7e0c3a5a5143a66dbee8af8e6eca
Author: JJoe2 
Date:   2017-02-01T12:19:54Z

Fixed LOG4NET-550




> Logging recursively from an Appender not supported for NET_4_0 and MONO_4_0
> ---
>
> Key: LOG4NET-550
> URL: https://issues.apache.org/jira/browse/LOG4NET-550
> Project: Log4net
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.0.7
>Reporter: Joe
>Priority: Minor
>
> When NET_4_0 or MONO_4_0 is defined, log4net uses a ReaderWriterLockSlim with 
> LockRecursionPolicy.NoRecursion.  As a result, any attempt to log recursively 
> from within an Appender fail: a System.Threading.LockRecursionException is 
> thrown and swallowed by the log4net Core.
> Other versions use a ReaderWriterLock and allow recursion.
> The following branch adds a unit test that shows this inconsistent behaviour. 
>  The test fails for NET_4_0 or MONO_4_0 and passes for other versions:
> https://github.com/JJoe2/log4net/tree/RecursiveLogging



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
I've spelled out 
https://github.com/apache/log4net/blob/6e8c0db1407a398fa64d72f89cf6b460ad209808/src/site/xdoc/release/framework-support.xml#L578
 which will become visible at 
http://logging.apache.org/log4net/release/framework-support.html once we cut 
the release. Also I'll make sure I list those limitations in the release notes 
and the announcement mail.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user SeanSnyders commented on the issue:

https://github.com/apache/log4net/pull/16
  
Right, okay.
Yes a a list of things not working would be great.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
Yes, that seems to be expected as 
`src/Util/PatternStringConverters/EnvironmentFolderPathPatternConverter` is 
among the excludes in 
https://github.com/apache/log4net/blob/trunk/netstandard/log4net/project.json#L32

We really need to document what is known to not work with .NET Core.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user SeanSnyders commented on the issue:

https://github.com/apache/log4net/pull/16
  
@bodewig Great, I'll try it again.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
@SeanSnyders I've updated the package at 
https://www.myget.org/feed/log4net-test/package/nuget/log4net (overwritten the 
original one)


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
I think c661441 holds the necessary changes. Unfortunately assembling the 
release bits for log4net still requires two different VMs and about an hour of 
time, so I may need a few days before I can re-create the package.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
The [nuspec](https://github.com/apache/log4net/blob/trunk/log4net.nuspec) 
doesn't list any dependencies, this is because all dependencies of log4net are 
part of the framework for the Mono and .NET versions.

Re-reading the nuspec schema we probably need to add a dependency `group` 
with the `targetFramework` set properly.  I'll try to see what the nuspec 
created with `dotnet pack` looks like.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user SeanSnyders commented on the issue:

https://github.com/apache/log4net/pull/16
  
@bodewig Yeah, I'm also trying to get my head around .Net Core project 
setup. Things have been quite a bit in flux!

I think one will need to spec the dependencies, no? I could have it by the 
tail, though
I'll try the other build you linked to as well.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
Many thanks @SeanSnyders . You are the first one actually given the 
binaries a try - or the first one who tells us so.

I've built the myget package using .NET Core 1.0.0 (SDK Preview 2), I 
really hope we don't need to provide assemblies built for different .NET Core 
1.x versions.

As for dependencies of the package, I didn't add any for the .NET Core 
version, maybe I should have. To be honest I'm far from an expert WRT .NET Core.

A preview build of the traditional distributions can be found in 
http://stefan.samaflost.de/staging/log4net-2.0.6/log4net-2.0.6-bin-newkey.zip - 
this contains the pdb file.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user SeanSnyders commented on the issue:

https://github.com/apache/log4net/pull/16
  
@bodewig I've downloaded[ your 2.0.6 version from myget 
](https://www.myget.org/feed/log4net-test/package/nuget/log4net )but get an 
exception thrown during init of my logger in a NetCoreApp 1.1.0 application 
targeting win10-x64.

Now, I'm a bit new to .Net Core, but my same code runs fine using latest 
2.0.5 on .Net 4.6.1.

Any chance of getting a `.pdb` of 2.0.6 so I can dig a bit deeper into 
where the exception occur with a sensible stack trace?

At a high level, I get these:

![image](https://cloud.githubusercontent.com/assets/1384135/20736496/d16db8a8-b70b-11e6-9926-242928f7f20e.png)

in my code on line 176  here:

![image](https://cloud.githubusercontent.com/assets/1384135/20736483/b6817fa2-b70b-11e6-9c00-cb9b179d99a1.png)

If I add the dependency of `System.Collections.NonGeneric 4.3.0` to my 
`project.json`, I still get an exception of:

![image](https://cloud.githubusercontent.com/assets/1384135/20736578/4d63a936-b70c-11e6-822b-f69e20e9a6b2.png)

Is the nuget package for 2.0.6 specifying all the dependencies? What am I 
missing here?






> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-530) Use UTC internally to avoid ambiguous timestamps

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-530:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/36
  
I've created LOG4NET-530 so it becomes easier to create the release notes 
by looking in one place only.

Many thanks, @JJoe2 


> Use UTC internally to avoid ambiguous timestamps
> 
>
> Key: LOG4NET-530
> URL: https://issues.apache.org/jira/browse/LOG4NET-530
> Project: Log4net
>  Issue Type: Improvement
>Affects Versions: 1.2.15
>Reporter: Stefan Bodewig
> Fix For: 2.0.6
>
>
> https://github.com/apache/log4net/pull/36



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-526) Add appSetting conversion pattern to PatternString

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-526:


Github user JJoe2 commented on the issue:

https://github.com/apache/log4net/pull/35
  
I’ll be happy to do the unit tests and possibly the doc.   Are suitable XML 
comments enough?

Now this is added, I’ll also be thinking about the next step, which is to 
allow the PatternString converter to be used in the XML configuration file for 
properties of types other than strings.
So that I can do something like:


   
   

Should be possible: basically be applying the PatternString conversion 
before converting to the target type of the property.

From: Stefan Bodewig [mailto:notificati...@github.com]
Sent: 26 October 2016 20:43
To: apache/log4net
Cc: JJoe2; Author
Subject: Re: [apache/log4net] Wip/app settings (#35)


I've added your converter, many thanks.

Tests would be good and we need documentation before we can close 
LOG4NET-526.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on 
GitHub, or 
mute the 
thread.



> Add appSetting conversion pattern to PatternString
> --
>
> Key: LOG4NET-526
> URL: https://issues.apache.org/jira/browse/LOG4NET-526
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.15
>Reporter: Joe
>Priority: Minor
>
> A common requirement is to be able to define a base directory for log files 
> that can be used by multiple FileAppenders.  In this way, the directory only 
> needs to be changed in one place.
> Today the typical solution is to use a PatternString with a property that is 
> set in code before log4net is configured, e.g.
>value="%property{LogDIr}MyFile.log"/>
> Suggested feature is to allow a conversion pattern that reads the base 
> directory name from an appSetting, e.g.:
>value="%appSetting{LogDIr}MyFile.log"/>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-526) Add appSetting conversion pattern to PatternString

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-526:


Github user asfgit closed the pull request at:

https://github.com/apache/log4net/pull/35


> Add appSetting conversion pattern to PatternString
> --
>
> Key: LOG4NET-526
> URL: https://issues.apache.org/jira/browse/LOG4NET-526
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.15
>Reporter: Joe
>Priority: Minor
>
> A common requirement is to be able to define a base directory for log files 
> that can be used by multiple FileAppenders.  In this way, the directory only 
> needs to be changed in one place.
> Today the typical solution is to use a PatternString with a property that is 
> set in code before log4net is configured, e.g.
>value="%property{LogDIr}MyFile.log"/>
> Suggested feature is to allow a conversion pattern that reads the base 
> directory name from an appSetting, e.g.:
>value="%appSetting{LogDIr}MyFile.log"/>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-526) Add appSetting conversion pattern to PatternString

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-526:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/35
  
I've added your converter, many thanks.

Tests would be good and we need documentation before we can close 
LOG4NET-526.


> Add appSetting conversion pattern to PatternString
> --
>
> Key: LOG4NET-526
> URL: https://issues.apache.org/jira/browse/LOG4NET-526
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.15
>Reporter: Joe
>Priority: Minor
>
> A common requirement is to be able to define a base directory for log files 
> that can be used by multiple FileAppenders.  In this way, the directory only 
> needs to be changed in one place.
> Today the typical solution is to use a PatternString with a property that is 
> set in code before log4net is configured, e.g.
>value="%property{LogDIr}MyFile.log"/>
> Suggested feature is to allow a conversion pattern that reads the base 
> directory name from an appSetting, e.g.:
>value="%appSetting{LogDIr}MyFile.log"/>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-511) API to flush appenders

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-511:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/37
  
Many thanks @JJoe2 and sorry for the hassle you had to go through.

tracked as LOG4NET-511 - https://issues.apache.org/jira/browse/LOG4NET-511




> API to flush appenders
> --
>
> Key: LOG4NET-511
> URL: https://issues.apache.org/jira/browse/LOG4NET-511
> Project: Log4net
>  Issue Type: Wish
>  Components: Appenders, Core
>Affects Versions: 1.2.15
> Environment: NA
>Reporter: Joe
>Priority: Minor
>
> I would like to see an API that flushes any appenders that have buffered 
> data. E.g. a method LogManager.Flush().  An application might call such a 
> method at regular intervals, e.g. on a Timer.
> A naive implementation with the current log4net would iterate through 
> appenders, looking for those that support flushing, and call the appender's 
> flush method, e.g.:
> foreach (IAppender appender in 
>  LogManager.GetRepository().GetAppenders())
> {
> BufferingAppenderSkeleton bas = appender 
> as BufferingAppenderSkeleton;  
> if (bas != null) bas.Flush();
> }
> But (a) I'm not sure this is thread-safe and (b) there are potentially other 
> appenders that may want to be able to flush data (e.g. a TextWriterAppender 
> with ImmediateFlush = false).
> The request consists of:
> - Add an interface, IFlushableAppender or equivalent, with a single method 
> Flush().
> - Implement this interface in all relevant appenders 
> (BufferingAppenderSkeleton, TextWriterAppender, ...)
> - Add a thread-safe static Flush() method to LogManager.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-511) API to flush appenders

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-511:


Github user JJoe2 closed the pull request at:

https://github.com/apache/log4net/pull/25


> API to flush appenders
> --
>
> Key: LOG4NET-511
> URL: https://issues.apache.org/jira/browse/LOG4NET-511
> Project: Log4net
>  Issue Type: Wish
>  Components: Appenders, Core
>Affects Versions: 1.2.15
> Environment: NA
>Reporter: Joe
>Priority: Minor
>
> I would like to see an API that flushes any appenders that have buffered 
> data. E.g. a method LogManager.Flush().  An application might call such a 
> method at regular intervals, e.g. on a Timer.
> A naive implementation with the current log4net would iterate through 
> appenders, looking for those that support flushing, and call the appender's 
> flush method, e.g.:
> foreach (IAppender appender in 
>  LogManager.GetRepository().GetAppenders())
> {
> BufferingAppenderSkeleton bas = appender 
> as BufferingAppenderSkeleton;  
> if (bas != null) bas.Flush();
> }
> But (a) I'm not sure this is thread-safe and (b) there are potentially other 
> appenders that may want to be able to flush data (e.g. a TextWriterAppender 
> with ImmediateFlush = false).
> The request consists of:
> - Add an interface, IFlushableAppender or equivalent, with a single method 
> Flush().
> - Implement this interface in all relevant appenders 
> (BufferingAppenderSkeleton, TextWriterAppender, ...)
> - Add a thread-safe static Flush() method to LogManager.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user derFunk commented on the issue:

https://github.com/apache/log4net/pull/16
  
Awesome, thanks.

I shared your cry for help on [Hacker 
News](https://news.ycombinator.com/item?id=12708507), maybe this gets some 
traction. Also you should maybe also add log4net here: 
http://up-for-grabs.net/#/tags/logging.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
@derFunk the mailing list comment was meant to say that there may be things 
going on that one might miss when not following the list. I must admit there 
isn't that much going on: 
https://blogs.apache.org/logging/entry/apache_log4net_needs_help

As for packages, I'm sorry, we're not prepared for that. We will be 
publishing the final release to nuget but the current test build looks like a 
real release internally, so we can't publish it there. I'd need to make myself 
familiar with myget first.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user derFunk commented on the issue:

https://github.com/apache/log4net/pull/16
  
@bodewig sorry for not using the mailing list ;) one last thing: I'd love 
to test basically right now. I don't have a public NuGet repo at hands, would 
it be possible for you to push it somewhere? NuGet.org/MyGet.org? I can test 
with my private repo until then, but it would be more convenient to have it 
publicly available.

Grüße aus München.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
log4net development is coordinated via the mailing list :-)


https://lists.apache.org/thread.html/3dafd7f063d6106ca9ca20379f5851a10e1588e9d1ce955d23e93a62@%3Clog4net-dev.logging.apache.org%3E

a test build has been available for about two weeks now, with nobody 
testing it, or so it seems.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user derFunk commented on the issue:

https://github.com/apache/log4net/pull/16
  
AFAIU it seems we could have a NuGet package release already, or at least a 
pre-release.
Is there anything else open we can help?
Unfortunately only the NuGet repo owner can push.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user NachbarsLumpi commented on the issue:

https://github.com/apache/log4net/pull/16
  
It is done when it is done. If you need it anytime sooner, get involved.

On 3 Oct 2016 4:22 p.m., "Ibrar Mumtaz"  wrote:

> Hi, do you guys have a release date for the new package? 2.0.6?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> , or 
mute
> the thread
> 

> .
>



> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user iby-dev commented on the issue:

https://github.com/apache/log4net/pull/16
  
Hi, do you guys have a release date for the new package? 2.0.6?


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-526) Add appSetting conversion pattern to PatternString

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-526:


GitHub user JJoe2 opened a pull request:

https://github.com/apache/log4net/pull/35

Wip/app settings

Implementation for LOG4NET-526

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/JJoe2/log4net wip/AppSettings

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/log4net/pull/35.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #35


commit a66d2fc61c4a1cfd8317aee41385ef6c43373ffc
Author: JoeJoe 
Date:   2016-04-22T19:21:07Z

Use UTC internally to avoid ambiguous times

commit 9e9f1759d6a80594cd2d12bd54a9e3af9e7cfaa0
Author: JoeJoe 
Date:   2016-04-23T19:58:36Z

Implement flushing of appenders that buffer data

commit 38fdfbaa7e9cd30e8a84fe90aa0ab12641b4db5f
Author: JoeJoe 
Date:   2016-10-02T17:12:33Z

Added AppSettingPatterConverter




> Add appSetting conversion pattern to PatternString
> --
>
> Key: LOG4NET-526
> URL: https://issues.apache.org/jira/browse/LOG4NET-526
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.15
>Reporter: Joe
>Priority: Minor
>
> A common requirement is to be able to define a base directory for log files 
> that can be used by multiple FileAppenders.  In this way, the directory only 
> needs to be changed in one place.
> Today the typical solution is to use a PatternString with a property that is 
> set in code before log4net is configured, e.g.
>value="%property{LogDIr}MyFile.log"/>
> Suggested feature is to allow a conversion pattern that reads the base 
> directory name from an appSetting, e.g.:
>value="%appSetting{LogDIr}MyFile.log"/>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user wjdavis5 commented on the issue:

https://github.com/apache/log4net/pull/16
  
Oh I see, I misread that their chart there. Thanks for clarifying.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user wjdavis5 commented on the issue:

https://github.com/apache/log4net/pull/16
  
Following the MSFT release yesterday - 
https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/

It looks like this should be bumped to Net Standard 1.6
I did so locally and the build output is good, I'll PR back to this fork to 
hopefully get this PR updated.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user wjdavis5 commented on the issue:

https://github.com/apache/log4net/pull/16
  
Hello, we are very patiently awaiting this next release. Thank you for 
putting this together.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 2.0.6
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
Thank you very much @chlowell 

@TAGC the code is in Apache's svn trunk and has been integrated with the 
build system by now. There are some lose ends and the biggest task is likely 
updating all documentation but I'm positive we aren't that far away from 
cutting the next release of log4net which will also include the .NET Core 
version. "not that far" may still get measured in weeks rather than days, 
though. 


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 1.2.16
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user TAGC commented on the issue:

https://github.com/apache/log4net/pull/16
  
That's for the info.  


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 1.2.16
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user chlowell commented on the issue:

https://github.com/apache/log4net/pull/16
  
This code has been merged into `trunk`. To my knowledge there's no 
published package, but you can build one with the dotnet CLI.

`ColoredConsoleAppender` isn't available for .NET Core because it uses 
Win32 APIs. `RollingFileAppender` is available, with the caveat that its file 
locking doesn't work on Linux.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 1.2.16
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user TAGC commented on the issue:

https://github.com/apache/log4net/pull/16
  
How far along is the .NET Core migration? I'm planning to migrate one of my 
projects that currently targets .NET Framework 4.5.2 to .NET Core and one of 
its dependencies is Log4Net. I only use `ColoredConsoleAppenders` and 
`RollingFileAppenders` - are these still available in the version targeting 
.NET Core?


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 1.2.16
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user chlowell commented on the issue:

https://github.com/apache/log4net/pull/16
  
No, there are significant differences. My first post details some important 
ones.

.NET Framework 4.6 implements `netstandard1.3`. This means it exposes all 
the APIs specified by `netstandard1.3` (and below). However, in terms of 
exposed APIs, `netstandard1.3` is a subset of .NET Framework 4.6. The latter 
exposes many APIs not specified by the former.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 1.2.16
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user NachbarsLumpi commented on the issue:

https://github.com/apache/log4net/pull/16
  
So that means that the log4net assembly targeting .net core has the same 
capabilities like the one targeting the .net framework 4.6 and differs only in 
the fact that it targets .net core with netstandard1.3?


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 1.2.16
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user chlowell commented on the issue:

https://github.com/apache/log4net/pull/16
  
@bodewig I chose the version number to prevent any confusion between 
prerelease and published packages. There's no reason not to change it before 
release.

I chose `netstandard1.3` because it's the lowest version with the required 
APIs. Targeting a higher version than necessary generally brings no benefit. 
For example, UAP 10.0 (the current version) supports `netstandard1.4`. If 
log4net targets `netstandard1.6`, UWP apps won't be able to use it (at least, 
not without a hack). There's more on this in the 
[docs](https://docs.microsoft.com/en-us/dotnet/articles/standard/library#net-platforms-support).

There's no need to worry about overriding--a project targeting .NET 
Framework 4.5 or below won't use the `netstandard1.3` assembly.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 1.2.16
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
I'm not sure this applies here as we are still creating specific assemblies 
for .NET 2.0 up to 4.5 - and all of them are superior to the .NET Core DLL as 
they provide an ADO.NET appender, for example. The assembly built here is only 
expected to be used for .NET Core. At least that's where I'd have expected it 
to get used.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 1.2.16
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user niemyjski commented on the issue:

https://github.com/apache/log4net/pull/16
  
The lower the .net standard you can target the more places it will run. 1.0 
can run every where (1.0, 1.6, etc). You should be targeting 1.3 here.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 1.2.16
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
I've just diffed chlowell:log4net-core-pcl against my svn working copy of 
trunk and it looks as if there have been changes after the PR which makes 
identifying misses more difficult. I'll apply #30 and then we can all go from 
there.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 1.2.16
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
@jasonwilliams200OK, thanks, but too late, I went off fixing it myself 
before I saw you comment. :-)

I'll diff my svn tree against a checkout of @chlowell's original branch to 
verify whether I missed more patch failures. It's pretty strange as I don't 
recall seeing any "hunk failed" messages.

BTW, this is the test result on Linux (Ubuntu 16.04, but I don't think it 
matters):

```
Errors and Failures
1) Failed : 
log4net.Tests.Appender.RollingFileAppenderTest.TestExclusiveLockLocks
  Log contents is not what is expected
  String lengths are both 38. Strings differ at index 0.
  Expected: "This is a message\nThis is a message 2\n"
  But was:  "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0This is a message 2\n"
  ---^
at log4net.Tests.Appender.RollingFileAppenderTest.AssertFileEquals(String 
filename, String contents) in 
/devel/ASF/log4net/trunk/tests/src/Appender/RollingFileAppenderTest.cs:line 1470
at log4net.Tests.Appender.RollingFileAppenderTest.TestExclusiveLockLocks() 
in /devel/ASF/log4net/trunk/tests/src/Appender/RollingFileAppenderTest.cs:line 
1570
Run Settings
WorkDirectory: /devel/ASF/log4net/trunk/netstandard
Test Run Summary
  Overall result: Failed
  Test Count: 145, Passed: 136, Failed: 1, Inconclusive: 0, Skipped: 8
Failed Tests - Failures: 1, Errors: 0, Invalid: 0
Skipped Tests - Ignored: 8, Explicit: 0, Other: 0
  Start time: 2016-08-13 16:05:11Z
End time: 2016-08-13 16:05:14Z
Duration: 2,964 seconds
Results saved as /devel/ASF/log4net/trunk/netstandard/TestResult.xml
SUMMARY: Total: 1 targets, Passed: 0, Failed: 1.
```


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 1.2.16
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
I've installed the Linux version, this is what happens for me:

```
Compiling log4net for .NETStandard,Version=v1.3
/usr/share/dotnet/dotnet compile-csc 
@/devel/ASF/log4net/trunk/netstandard/log4net/obj/Debug/netstandard1.3/dotnet-compile.rsp
 returned Exit Code 1
/devel/ASF/log4net/trunk/src/Appender/FileAppender.cs(164,33): error 
CS0115: 'FileAppender.LockingStream.BeginRead(byte[], int, int, AsyncCallback, 
object)': no suitable method found to override
/devel/ASF/log4net/trunk/src/Appender/FileAppender.cs(175,33): error 
CS0115: 'FileAppender.LockingStream.BeginWrite(byte[], int, int, AsyncCallback, 
object)': no suitable method found to override
/devel/ASF/log4net/trunk/src/Appender/FileAppender.cs(183,25): error 
CS0115: 'FileAppender.LockingStream.Close()': no suitable method found to 
override
/devel/ASF/log4net/trunk/src/Appender/FileAppender.cs(188,24): error 
CS0115: 'FileAppender.LockingStream.EndRead(IAsyncResult)': no suitable method 
found to override
/devel/ASF/log4net/trunk/src/Appender/FileAppender.cs(193,25): error 
CS0115: 'FileAppender.LockingStream.EndWrite(IAsyncResult)': no suitable method 
found to override

Compilation failed.
0 Warning(s)
5 Error(s)
```

I'll double check whether I've missed some changes to `FileAppender`.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 1.2.16
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user jasonwilliams200OK commented on the issue:

https://github.com/apache/log4net/pull/16
  
@bodewig, #30 fixed exactly this issue. Can you try with my branch?


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 1.2.16
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user jasonwilliams200OK commented on the issue:

https://github.com/apache/log4net/pull/16
  
Fixed the build breakage and feedback in #30.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Fix For: 1.2.16
>
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-518) Filters don't work when use multiple.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-518:


Github user asfgit closed the pull request at:

https://github.com/apache/log4net/pull/27


> Filters don't work when use multiple.
> -
>
> Key: LOG4NET-518
> URL: https://issues.apache.org/jira/browse/LOG4NET-518
> Project: Log4net
>  Issue Type: Bug
>  Components: Other
>Affects Versions: 1.2.15
>Reporter: huiqiang yan
>Assignee: Dominik Psenner
>
> I have an application managed multiple AppDomains, and my master application 
> can get messages from all appDomain, then log them separately.
> I create appenders from each appDomains and use the 'domain name’ and 'log 
> level' to discriminate。
> RollingFileAppender appender = new RollingFileAppender();
> appender.AddFilter(new LevelRangeFilter
> {
> LevelMin = Level.Info,
> LevelMax = Level.Info,
> AcceptOnMatch = false,
> Next = new LoggerMatchFilter
> {
> LoggerToMatch = name,
> AcceptOnMatch = true
> }
> });
> when name doesn't match, the If statement in filter LoggerMatchFilter file at 
> line 140 ,I think it means match or doesn't match, it should be deny in else 
> statement.
> AcceptOnMatch only use when the match is passed ,it means if should return 
> Accept when matched,and when it is false then return Neutral.
> Not only LoggerMatchFilter has this problem, others too. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-518) Filters don't work when use multiple.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-518:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/27
  
has been rejected by Dominik Psenner in 
https://issues.apache.org/jira/browse/LOG4NET-518


> Filters don't work when use multiple.
> -
>
> Key: LOG4NET-518
> URL: https://issues.apache.org/jira/browse/LOG4NET-518
> Project: Log4net
>  Issue Type: Bug
>  Components: Other
>Affects Versions: 1.2.15
>Reporter: huiqiang yan
>Assignee: Dominik Psenner
>
> I have an application managed multiple AppDomains, and my master application 
> can get messages from all appDomain, then log them separately.
> I create appenders from each appDomains and use the 'domain name’ and 'log 
> level' to discriminate。
> RollingFileAppender appender = new RollingFileAppender();
> appender.AddFilter(new LevelRangeFilter
> {
> LevelMin = Level.Info,
> LevelMax = Level.Info,
> AcceptOnMatch = false,
> Next = new LoggerMatchFilter
> {
> LoggerToMatch = name,
> AcceptOnMatch = true
> }
> });
> when name doesn't match, the If statement in filter LoggerMatchFilter file at 
> line 140 ,I think it means match or doesn't match, it should be deny in else 
> statement.
> AcceptOnMatch only use when the match is passed ,it means if should return 
> Accept when matched,and when it is false then return Neutral.
> Not only LoggerMatchFilter has this problem, others too. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user jasonwilliams200OK commented on the issue:

https://github.com/apache/log4net/pull/16
  
Thanks a lot @bodewig! I am definitely willing to participate. I will test 
out the master and try to incorporate the feedback in subsequent PR pronto 
(before you start cutting the release :stuck_out_tongue_winking_eye:). I have 
subscribed to log4net-dev mailing list.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
Many thanks for your persistence.

I have applied the patch as is as it didn't break anything of the existing 
build. But I haven't even tried to build the .NET Core part itself - I'll do so 
later, and try to figure out how to cut releases that contain the .NET Core 
assembly as well as the current process is centered around NAnt.

I'd like to invite anybody interested in keeping log4net moving to join the 
log4net-dev mailing list and lend a hand. We are severely understaffed and can 
use any help.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user asfgit closed the pull request at:

https://github.com/apache/log4net/pull/16


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user jasonwilliams200OK commented on a diff in the pull request:

https://github.com/apache/log4net/pull/16#discussion_r74683879
  
--- Diff: src/Util/PatternStringConverters/NewLinePatternConverter.cs ---
@@ -72,6 +75,16 @@ internal sealed class NewLinePatternConverter : 
LiteralPatternConverter, IOption
/// 
public void ActivateOptions()
{
+#if NETSTANDARD1_3
+   if 
(CultureInfo.InvariantCulture.CompareInfo.Compare(Option, "DOS", 
CompareOptions.IgnoreCase) == 0)
+   {
+   Option = "\r\n";
+   }
+   else if 
(CultureInfo.InvariantCulture.CompareInfo.Compare(Option, "UNIX", 
CompareOptions.IgnoreCase) == 0)
--- End diff --

@chlowell, do you think it's a good idea to instead of dogfooding 
`string.Compare(strA, strB, InvariantCulture) == 0` pattern with `CultureInfo` 
comparer, use common denominator `strA.ToUpperInvariant() == 
strB.ToUpperInvariant()` and remove the preprocessor all over the place as part 
of this PR? IMO, this will clean up quite a bit. If you want, I can send a PR 
to your `log4net-core-pcl` branch, then you would just need to update the JIRA 
patch. :)


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user jasonwilliams200OK commented on a diff in the pull request:

https://github.com/apache/log4net/pull/16#discussion_r73228215
  
--- Diff: netstandard/log4net/project.json ---
@@ -0,0 +1,94 @@
+{
+  "name": "log4net",
+  "version": "3.0.0",
+  "frameworks": {
+"netstandard1.3": {
+  "buildOptions": {
+"compile": {
+  "include": [ "*.cs", "../../src/**/*.cs" ],
+  "exclude": [
+"../../src/Appender/AdoNetAppender.cs",
+"../../src/Appender/AspNetTraceAppender.cs",
+"../../src/Appender/ColoredConsoleAppender.cs",
+"../../src/Appender/EventLogAppender.cs",
+"../../src/Appender/NetSendAppender.cs",
+"../../src/Appender/RemotingAppender.cs",
+"../../src/Appender/SmtpAppender.cs",
+"../../src/LogicalThreadContext.cs",
+"../../src/Config/DOMConfigurator.cs",
+"../../src/Config/DOMConfiguratorAttribute.cs",
+"../../src/Config/Log4NetConfigurationSectionHandler.cs",
+"../../src/Layout/Pattern/AspNetCachePatternConverter.cs",
+"../../src/Layout/Pattern/AspNetContextPatternConverter.cs",
+"../../src/Layout/Pattern/AspNetPatternConverter.cs",
+"../../src/Layout/Pattern/AspNetRequestPatternConverter.cs",
+"../../src/Layout/Pattern/AspNetSessionPatternConverter.cs",
+"../../src/Layout/Pattern/StackTraceDetailPatternConverter.cs",
+"../../src/Layout/Pattern/StackTracePatternConverter.cs",
+"../../src/Plugin/RemoteLoggingServerPlugin.cs",
+
"../../src/Util/PatternStringConverters/EnvironmentFolderPathPatternConverter.cs",
+"../../src/Util/LogicalThreadContextProperties.cs",
+"../../src/Util/LogicalThreadContextStacks.cs",
+"../../src/Util/NativeError.cs",
+"../../src/Util/WindowsSecurityContext.cs"
+  ]
+},
+"define": [ "HAS_READERWRITERLOCKSLIM", "NETSTANDARD1_3" ]
--- End diff --

`NETSTANDARD1_3` definition is redundant here.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
> Attachments: LOG4NET-467.patch
>
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user chlowell commented on a diff in the pull request:

https://github.com/apache/log4net/pull/16#discussion_r70652017
  
--- Diff: src/Util/ReadOnlyPropertiesDictionary.cs ---
@@ -215,8 +216,13 @@ public virtual void GetObjectData(SerializationInfo 
info, StreamingContext conte
string entryKey = entry.Key as string;
object entryValue = entry.Value;
 
-   // If value is serializable then we add it to 
the list
-   if (entryKey != null && entryValue != null && 
entryValue.GetType().IsSerializable)
+// If value is serializable then we add it to the list
+#if NETSTANDARD1_3
+   bool isSerializable = 
entryValue.GetType().GetTypeInfo().IsSerializable;
+#else
+bool isSerializable = entryValue.GetType().IsSerializable;
+#endif
+if (entryKey != null && entryValue != null && 
isSerializable)
{
--- End diff --

The original code mixes tabs and spaces freely. I tried to remain 
consistent with that to limit whitespace noise in the diff. I'll normalize the 
lines you've called out; thanks for the attention to detail.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user jasonwilliams200OK commented on the issue:

https://github.com/apache/log4net/pull/16
  
> @arkadiuszwojcik the goal of this PR is to make log4net portable across 
.NET Core platforms. Implementing those abstractions could be useful, but doing 
so wouldn't enable consuming log4net on additional platforms.

I agree and I think that can be a separate repo / package, something like 
log4net.Extensions.Logging. However, having this Extensions package first hand 
from original vendor (Apache) is vital on multiple accounts.

---

Separately, can this PR get some prio love from the reviews please? All the 
providers listed here: https://github.com/aspnet/Logging#providers, are not as 
popular as log4net and we (folks running stuff on dotnet core) hoping to get 
our hands on apache/log4net bits.

@chlowell, could you please prepare a SVN patch for the reviewers? We can 
always have subsequent PRs to refine stuff. If you are aiming to add CI setup 
for .NET Core TxM as part of this PR, feel free to grab Travis/AppVeyor bits 
from https://github.com/autofac/Autofac.Extras.Moq/pull/6/files.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user stuartd commented on the issue:

https://github.com/apache/log4net/pull/16
  

[ToUpperInvariant](http://stackoverflow.com/questions/2801508/what-is-wrong-with-tolowerinvariant)
 is preferable



> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user niemyjski commented on a diff in the pull request:

https://github.com/apache/log4net/pull/16#discussion_r70623307
  
--- Diff: src/Util/PatternStringConverters/NewLinePatternConverter.cs ---
@@ -72,6 +75,16 @@ internal sealed class NewLinePatternConverter : 
LiteralPatternConverter, IOption
/// 
public void ActivateOptions()
{
+#if NETSTANDARD1_3
+   if 
(CultureInfo.InvariantCulture.CompareInfo.Compare(Option, "DOS", 
CompareOptions.IgnoreCase) == 0)
+   {
+   Option = "\r\n";
+   }
+   else if 
(CultureInfo.InvariantCulture.CompareInfo.Compare(Option, "UNIX", 
CompareOptions.IgnoreCase) == 0)
--- End diff --

ToLowerInvariant()


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user jasonwilliams200OK commented on a diff in the pull request:

https://github.com/apache/log4net/pull/16#discussion_r70601430
  
--- Diff: src/Util/PatternStringConverters/NewLinePatternConverter.cs ---
@@ -72,6 +75,16 @@ internal sealed class NewLinePatternConverter : 
LiteralPatternConverter, IOption
/// 
public void ActivateOptions()
{
+#if NETSTANDARD1_3
+   if 
(CultureInfo.InvariantCulture.CompareInfo.Compare(Option, "DOS", 
CompareOptions.IgnoreCase) == 0)
+   {
+   Option = "\r\n";
+   }
+   else if 
(CultureInfo.InvariantCulture.CompareInfo.Compare(Option, "UNIX", 
CompareOptions.IgnoreCase) == 0)
--- End diff --

Should we just ToLower(), compare with `==` and get rid of the 
preprocessors for all Compare()-like code?


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user jasonwilliams200OK commented on a diff in the pull request:

https://github.com/apache/log4net/pull/16#discussion_r70601024
  
--- Diff: src/Util/ReadOnlyPropertiesDictionary.cs ---
@@ -215,8 +216,13 @@ public virtual void GetObjectData(SerializationInfo 
info, StreamingContext conte
string entryKey = entry.Key as string;
object entryValue = entry.Value;
 
-   // If value is serializable then we add it to 
the list
-   if (entryKey != null && entryValue != null && 
entryValue.GetType().IsSerializable)
+// If value is serializable then we add it to the list
+#if NETSTANDARD1_3
+   bool isSerializable = 
entryValue.GetType().GetTypeInfo().IsSerializable;
+#else
+bool isSerializable = entryValue.GetType().IsSerializable;
+#endif
+if (entryKey != null && entryValue != null && 
isSerializable)
{
--- End diff --

nit: indentation under `#if` `#else` and that of `if (entryKey` is off


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user jasonwilliams200OK commented on a diff in the pull request:

https://github.com/apache/log4net/pull/16#discussion_r70600774
  
--- Diff: tests/src/Utils.cs ---
@@ -105,7 +114,28 @@ private static Type[] GetTypesArray(object[] args)
 internal static void RemovePropertyFromAllContexts() {
 GlobalContext.Properties.Remove(PROPERTY_KEY);
 ThreadContext.Properties.Remove(PROPERTY_KEY);
+#if !(NETCF || NETSTANDARD1_3)
 LogicalThreadContext.Properties.Remove(PROPERTY_KEY);
+#endif
 }
-   }
+
+// Wrappers because repository/logger retrieval APIs require an 
Assembly argument on NETSTANDARD1_3
+internal static ILog GetLogger(string name)
+{
+#if NETSTANDARD1_3
+return 
LogManager.GetLogger(typeof(Utils).GetTypeInfo().Assembly, name);
+#else
+   return LogManager.GetLogger(name);
+#endif
--- End diff --

nit: indentation of either one of two return statements is off


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user chlowell commented on the issue:

https://github.com/apache/log4net/pull/16
  
I updated this branch for .NET Core 1.0 rather than creating a new PR. The 
branch name is unfortunate--there's no longer a PCL involved--but I hope 
keeping this open is convenient for those watching.

@arkadiuszwojcik the goal of this PR is to make log4net portable across 
.NET Core platforms. Implementing those abstractions could be useful, but doing 
so wouldn't enable consuming log4net on additional platforms.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user arkadiuszwojcik commented on the issue:

https://github.com/apache/log4net/pull/16
  
I suggest all of you switch to:

https://www.nuget.org/packages/Microsoft.Extensions.Logging.Abstractions/

and create log4net port for that. Actually it is quite easy to create it on 
your own.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user pantonis commented on the issue:

https://github.com/apache/log4net/pull/16
  
+1


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-518) Filters don't work when use multiple.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-518:


GitHub user efenghuo opened a pull request:

https://github.com/apache/log4net/pull/27

fixed issue LOG4NET-518.

when filter passed, should return accept or neutral(then next filter to 
work),else return deny

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/efenghuo/log4net trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/log4net/pull/27.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #27


commit e86b0fb87b3efec5a9ccfe0c6213436c82d230db
Author: yanhuiqiang 
Date:   2016-06-21T07:05:28Z

fixed issue LOG4NET-518.




> Filters don't work when use multiple.
> -
>
> Key: LOG4NET-518
> URL: https://issues.apache.org/jira/browse/LOG4NET-518
> Project: Log4net
>  Issue Type: Bug
>  Components: Other
>Affects Versions: 1.2.15
>Reporter: huiqiang yan
>
> I have an application managed multiple AppDomains, and my master application 
> can get messages from all appDomain, then log them separately.
> I create appenders from each appDomains and use the 'domain name’ and 'log 
> level' to discriminate。
> RollingFileAppender appender = new RollingFileAppender();
> appender.AddFilter(new LevelRangeFilter
> {
> LevelMin = Level.Info,
> LevelMax = Level.Info,
> AcceptOnMatch = false,
> Next = new LoggerMatchFilter
> {
> LoggerToMatch = name,
> AcceptOnMatch = true
> }
> });
> when name doesn't match, the If statement in filter LoggerMatchFilter file at 
> line 140 ,I think it means match or doesn't match, it should be deny in else 
> statement.
> AcceptOnMatch only use when the match is passed ,it means if should return 
> Accept when matched,and when it is false then return Neutral.
> Not only LoggerMatchFilter has this problem, others too. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user niemyjski commented on the issue:

https://github.com/apache/log4net/pull/16
  
+1 I'm also needing this for our oss projects that depend on log4net. Would 
be great to get this on the lowest .net standard possible.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the issue:

https://github.com/apache/log4net/pull/16
  
so far there haven't been any concrete plans beyond this PR


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user StrangeWill commented on the pull request:

https://github.com/apache/log4net/pull/16
  
@bodewig _Hopefully_ there shouldn't be much flux between RC2 and Final 
(well at least we were told porting from RC2 -> Final won't be nearly as bad as 
RC1 -> RC2 was, and it wasn't *that* bad), though I am struggling myself with 
System.Diagnostics.Stacktrace being gutted on one of my own projects. I can 
totally understand the hesitation though especially with a project like this.

I'll be keeping my eye out for support for .NET Core on log4net, I'm just 
not nearly as happy with any of the other solutions.

---

The other interesting question is whether or not log4net on .NET Core is 
going to support the new json configuration files or still require XML files 
out of the box.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user chlowell commented on the pull request:

https://github.com/apache/log4net/pull/16#issuecomment-222199688
  
I have another branch on my fork (`dotnetcore-rc2`) which builds with RC2 
tools, and has some improvements over the code here. A few tests are broken due 
to executing with NUnitLite. Once the NUnit runner is updated for RC2 
(nunit/nunit#1371), I'll open a new PR.


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user chester89 commented on the pull request:

https://github.com/apache/log4net/pull/16#issuecomment-222102483
  
@chlowell any updates on this?


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-512) Thread safety issue in Hierarchy.cs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-512:


Github user JJoe2 commented on the pull request:

https://github.com/apache/log4net/pull/25#issuecomment-214260923
  
Added two commits including a fix for 
https://issues.apache.org/jira/browse/LOG4NET-512


> Thread safety issue in Hierarchy.cs
> ---
>
> Key: LOG4NET-512
> URL: https://issues.apache.org/jira/browse/LOG4NET-512
> Project: Log4net
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.2.15
>Reporter: Joe
>Priority: Minor
>
> From inspecting the source code I believe there is a threading bug in the 
> Hierarchy class.  Both of the methods Exists and GetCurrentLoggers access the 
> internal hashtable m_ht without locking.
> Impact is minor as both these methods are probably rarely called by third 
> party code, and since they do not modify state, the worst that can happen is 
> an unexpected exception.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-511) API to flush appenders

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-511:


GitHub user JJoe2 opened a pull request:

https://github.com/apache/log4net/pull/25

API to flush appenders that buffer logging data

Implementation of https://issues.apache.org/jira/browse/LOG4NET-511

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/JJoe2/log4net wip/Flush

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/log4net/pull/25.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #25


commit a66d2fc61c4a1cfd8317aee41385ef6c43373ffc
Author: JoeJoe 
Date:   2016-04-22T19:21:07Z

Use UTC internally to avoid ambiguous times

commit 9e9f1759d6a80594cd2d12bd54a9e3af9e7cfaa0
Author: JoeJoe 
Date:   2016-04-23T19:58:36Z

Implement flushing of appenders that buffer data




> API to flush appenders
> --
>
> Key: LOG4NET-511
> URL: https://issues.apache.org/jira/browse/LOG4NET-511
> Project: Log4net
>  Issue Type: Wish
>  Components: Appenders, Core
>Affects Versions: 1.2.15
> Environment: NA
>Reporter: Joe
>Priority: Minor
> Fix For: 1.2.16
>
>
> I would like to see an API that flushes any appenders that have buffered 
> data. E.g. a method LogManager.Flush().  An application might call such a 
> method at regular intervals, e.g. on a Timer.
> A naive implementation with the current log4net would iterate through 
> appenders, looking for those that support flushing, and call the appender's 
> flush method, e.g.:
> foreach (IAppender appender in 
>  LogManager.GetRepository().GetAppenders())
> {
> BufferingAppenderSkeleton bas = appender 
> as BufferingAppenderSkeleton;  
> if (bas != null) bas.Flush();
> }
> But (a) I'm not sure this is thread-safe and (b) there are potentially other 
> appenders that may want to be able to flush data (e.g. a TextWriterAppender 
> with ImmediateFlush = false).
> The request consists of:
> - Add an interface, IFlushableAppender or equivalent, with a single method 
> Flush().
> - Implement this interface in all relevant appenders 
> (BufferingAppenderSkeleton, TextWriterAppender, ...)
> - Add a thread-safe static Flush() method to LogManager.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


Github user bodewig commented on the pull request:

https://github.com/apache/log4net/pull/16#issuecomment-163839682
  
referenced in LOG4NET-467 https://issues.apache.org/jira/browse/LOG4NET-467


> Is .NET Core, will be supported in the near future, or not
> --
>
> Key: LOG4NET-467
> URL: https://issues.apache.org/jira/browse/LOG4NET-467
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.13
>Reporter: san kan
>  Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-473) Option for file extension in SmtpPickupDirAppender

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-473:


GitHub user albinsunnanbo opened a pull request:

https://github.com/apache/log4net/pull/19

File extension for smtp appender

Add a configuration option for adding a file extension to the generated 
mails.
Updated patch from https://issues.apache.org/jira/browse/LOG4NET-473

Based on https://github.com/apache/log4net/pull/17

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/albinsunnanbo/log4net 
FileExtensionForSmtpAppender

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/log4net/pull/19.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #19


commit 899579668d6b75711a425005fa4861fdeb3932e1
Author: Albin Sunnanbo 
Date:   2015-11-01T09:35:54Z

Create basic SmtpPickupDirAppenderTest

commit 9f0a9e0857d58cec19673de95c2a28292dfdc171
Author: Albin Sunnanbo 
Date:   2015-10-31T21:32:41Z

Add option for file extensions to the SmtpPickupDirAppender

 - Especially on Windows file extensions are very handy, if you give the 
output files the `eml` extension you can just double click the file to open the 
mail in outlook.
 - I have added a `FileExtension` option to the `SmtpPickupDirAppender` 
that can be used to specify a file extension for the generated files.
 - Although a default value of `eml` would be nice I have preserved 
backwards compatibility of no file extension by default.




> Option for file extension in SmtpPickupDirAppender
> --
>
> Key: LOG4NET-473
> URL: https://issues.apache.org/jira/browse/LOG4NET-473
> Project: Log4net
>  Issue Type: New Feature
>Affects Versions: 1.2.13
>Reporter: Albin Sunnanbo
> Attachments: SmtpPickupDirAppender-fileextension.patch
>
>
> Especially on Windows file extensions are very handy, if you give the output 
> files the `eml` extension you can just double click the file to open the mail 
> in outlook.
> I have added a `FileExtension` option to the `SmtpPickupDirAppender` that can 
> be used to specify a file extension for the generated files.
> Although a default value of `eml` would be nice I have preserved backwards 
> compatibility of no file extension by default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-457) SMTP Appender should trim leading and trailing separators from address fields

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-457:


Github user bodewig commented on the pull request:

https://github.com/apache/log4net/pull/13#issuecomment-78291627
  
tracked by LOG4NET-457


 SMTP Appender should trim leading and trailing separators from address fields
 -

 Key: LOG4NET-457
 URL: https://issues.apache.org/jira/browse/LOG4NET-457
 Project: Log4net
  Issue Type: Improvement
  Components: Appenders
Affects Versions: 1.2.13
Reporter: Stefan Bodewig
 Fix For: 1.3.0


 see https://github.com/apache/log4net/pull/13



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-455) LogicalThreadContext does not flow correctly through async/await

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-455:


Github user bodewig commented on the pull request:

https://github.com/apache/log4net/pull/12#issuecomment-77686089
  
I'm fine with the first batch of changes you propose but don't think we 
should thrown an exception on .NET 4.0.  I've opened 
[LOG4NET-455](https://issues.apache.org/jira/browse/LOG4NET-455) for tracking 
this PR.


 LogicalThreadContext does not flow correctly through async/await 
 -

 Key: LOG4NET-455
 URL: https://issues.apache.org/jira/browse/LOG4NET-455
 Project: Log4net
  Issue Type: Bug
Reporter: Stefan Bodewig

 This ticket accompanies github pull request #12 
 https://github.com/apache/log4net/pull/12



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LOG4NET-428) Sysinternals Process Monitor appender

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-428:


GitHub user zippy1981 opened a pull request:

https://github.com/apache/log4net/pull/9

Implement LOG4NET-428 ProcMonAppender

I am trying to figure out how to best unit test this.In other words, I need 
to learn how to automate process monitor, and parse csv files.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/zippy1981/log4net ProcMonAppender

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/log4net/pull/9.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #9


commit 4a1f5197de1501a732a3b93f301f74764447673b
Author: Justin Dearing zippy1...@gmail.com
Date:   2014-03-20T23:12:19Z

First version of ProcMonAppender




 Sysinternals Process Monitor appender
 -

 Key: LOG4NET-428
 URL: https://issues.apache.org/jira/browse/LOG4NET-428
 Project: Log4net
  Issue Type: New Feature
  Components: Appenders
Affects Versions: 1.2.13
 Environment: Any version of windows than can run process monitor
Reporter: Justin Dearing
   Original Estimate: 1h
  Remaining Estimate: 1h

 Wintellect released some code that allows you to send trace messages to 
 procmon. Using that code as an example I wrote a completely managed log4net 
 appender (with the help of PInvoke). John has stated he is ok with me 
 releasing my code to you guys and he'll sign something if he has to.



--
This message was sent by Atlassian JIRA
(v6.2#6252)