[
https://issues.apache.org/jira/browse/LOG4NET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489373#comment-15489373
]
ASF GitHub Bot commented on LOG4NET-467:
Github user bodewig commented on the iss
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
[
https://issues.apache.org/jira/browse/LOG4NET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487988#comment-15487988
]
ASF GitHub Bot commented on LOG4NET-467:
Github user TAGC commented on the issue:
Github user TAGC commented on the issue:
https://github.com/apache/log4net/pull/16
That's for the info. ð
---
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 s
[
https://issues.apache.org/jira/browse/LOG4NET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487962#comment-15487962
]
ASF GitHub Bot commented on LOG4NET-467:
Github user chlowell commented on the is
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 becaus
[
https://issues.apache.org/jira/browse/LOG4NET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487929#comment-15487929
]
ASF GitHub Bot commented on LOG4NET-467:
Github user TAGC commented on the issue:
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 `ColoredC
[
https://issues.apache.org/jira/browse/LOG4NET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487892#comment-15487892
]
ASF GitHub Bot commented on LOG4NET-467:
Github user chlowell commented on the is
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 `netstandar
[
https://issues.apache.org/jira/browse/LOG4NET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487841#comment-15487841
]
ASF GitHub Bot commented on LOG4NET-467:
Github user NachbarsLumpi commented on t
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 n
[
https://issues.apache.org/jira/browse/LOG4NET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487744#comment-15487744
]
ASF GitHub Bot commented on LOG4NET-467:
Github user chlowell commented on the is
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 i
[
https://issues.apache.org/jira/browse/LOG4NET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487281#comment-15487281
]
ASF GitHub Bot commented on LOG4NET-467:
Github user bodewig commented on the iss
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
16 matches
Mail list logo
