[
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 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)
