[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

2017-03-02 Thread NachbarsLumpi
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.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


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

2017-03-02 Thread 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)


[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

2017-03-02 Thread robcube
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)
```



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


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

2017-03-02 Thread 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)