[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support
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. ---
[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support
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" <notificati...@github.com> 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 > <https://github.com/apache/log4net/pull/16#issuecomment-251118857>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AIID6uKBzeKNLRNv1afKYssvwT7m16FCks5qwQ-ggaJpZM4GYooH> > . > --- 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. ---
[GitHub] log4net pull request: added CF 3.5 Support
Github user NachbarsLumpi commented on the pull request: https://github.com/apache/log4net/pull/21#issuecomment-172776602 Your patch added file watch support? Didn't see that when I reviewed your patch. Would you mind to split the commit into two to make it clearer? --- 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. ---
[GitHub] log4net pull request: added CF 3.5 Support
Github user NachbarsLumpi commented on the pull request: https://github.com/apache/log4net/pull/21#issuecomment-172764108 This looks good. Is there a special reason why you require support for CF 3.5? CF 2.0 libraries can be referenced from a CF 3.5 application without problems. --- 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. ---
[GitHub] log4net pull request: Add ColoredSmtpAppender. allow user send col...
Github user NachbarsLumpi commented on the pull request: https://github.com/apache/log4net/pull/7#issuecomment-172766709 Actually, this problem should be solved with a custom ILayout implementation that is assigned to the appender. You can then change the look of the email by changing the layouts properties: ILayout.ContentType = "text/html"; ILayout.Header = ""; ILayout.Footer = ""; and by overriding this method the look of every log event can be rendered to html: void Format(TextWriter writer, 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. ---
