[jira] [Commented] (LOG4NET-554) LogicalThreadContext was removed in .NETStandard
[ https://issues.apache.org/jira/browse/LOG4NET-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872182#comment-15872182 ] Dominik Psenner commented on LOG4NET-554: - Interesting, I look forward seeing a patch! > LogicalThreadContext was removed in .NETStandard > > > Key: LOG4NET-554 > URL: https://issues.apache.org/jira/browse/LOG4NET-554 > Project: Log4net > Issue Type: Bug > Components: Builds >Affects Versions: 2.0.6, 2.0.7 > Environment: .NETStandard1.3 >Reporter: Thomas Clegg > Original Estimate: 504h > Remaining Estimate: 504h > > LogicalThreadContext was excluded from dotnetcore version due to > System.Runtime.Remoting.Messaging no longer being available going forward. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (LOG4NET-554) LogicalThreadContext was removed in .NETStandard
[ https://issues.apache.org/jira/browse/LOG4NET-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872154#comment-15872154 ] Thomas Clegg commented on LOG4NET-554: -- My team's use case is highly dependent on this functionality and as such we obviously don't want to lose it. The same functionality should be available via AsyncLocal which is supported in .NET 4.6 and above. I'm actively working on a patch to get things working again. > LogicalThreadContext was removed in .NETStandard > > > Key: LOG4NET-554 > URL: https://issues.apache.org/jira/browse/LOG4NET-554 > Project: Log4net > Issue Type: Bug > Components: Builds >Affects Versions: 2.0.6, 2.0.7 > Environment: .NETStandard1.3 >Reporter: Thomas Clegg > Original Estimate: 504h > Remaining Estimate: 504h > > LogicalThreadContext was excluded from dotnetcore version due to > System.Runtime.Remoting.Messaging no longer being available going forward. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
