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.
---
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.
---
