[
https://issues.apache.org/jira/browse/LOG4NET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374783#comment-15374783
]
ASF GitHub Bot commented on LOG4NET-467:
----------------------------------------
Github user jasonwilliams200OK commented on a diff in the pull request:
https://github.com/apache/log4net/pull/16#discussion_r70599902
--- Diff: src/Appender/AppenderCollection.cs ---
@@ -26,7 +26,10 @@ namespace log4net.Appender
/// A strongly-typed collection of <see cref="IAppender"/> objects.
/// </summary>
/// <author>Nicko Cadell</author>
- public class AppenderCollection : ICollection, IList, IEnumerable,
ICloneable
+ public class AppenderCollection : ICollection, IList, IEnumerable
+#if !NETSTANDARD1_3
+ , ICloneable
--- End diff --
Note that ICloneable is coming back.
https://github.com/dotnet/corefx/pull/9970
If the new contract doesn't support NETSTANDARD1_3, and we do want to
support this TxM, then the best way in the future would be to also add
`NETSTANDARD1_<whatever>` in the project.json which exposes IColeable interface
on public surface area.
> 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)
