[
https://issues.apache.org/jira/browse/LOG4NET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305835#comment-15305835
]
ASF GitHub Bot commented on LOG4NET-467:
----------------------------------------
Github user bodewig commented on the pull request:
https://github.com/apache/log4net/pull/16#issuecomment-222350005
Please note I'm just one voice others may think differently about this.
Given the amount of flux that's going on I'm a bit reluctant to adapt to .NET
Core before 1.0 is final.
And once it is, in the light of
https://blogs.msdn.microsoft.com/dotnet/2016/05/27/making-it-easier-to-port-to-net-core/
I'm not sure whether it wouldn't be better to wait even a bit longer. The
current patch throws out all serialization which will become available in a
successor of .NET Core again, maybe the workarounds for
`System.Diagnostics.StackTrace` and `Assembly.GetCallingAssembly` won't be
needed any longer either.
> 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)
