[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4net-dev
Subject:    [jira] [Commented] (LOG4NET-542) LogManager.GetLogger(String) is missing in .NET Standard library ve
From:       "Stefan Bodewig (JIRA)" <jira () apache ! org>
Date:       2017-01-09 7:01:58
Message-ID: JIRA.13032560.1483713080000.681932.1483945318595 () Atlassian ! JIRA
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/LOG4NET-542?page=com.atlassian.jira.plugin \
.system.issuetabpanels:comment-tabpanel&focusedCommentId=15810867#comment-15810867 ] 

Stefan Bodewig commented on LOG4NET-542:
----------------------------------------

{{GetLogger}} needs to know which {{Repository}} to use when looking up the logger, \
repositories in turn get initialized based on assemblies (holding log4net \
attributes).

The {{GetLogger(string)}} method is a shortcut for \
{{GetLogger(Assembly.GetCallingAssembly(), name)}} and \
{{Assembly.GetCallingAssembly()}} is not available in .NETStandard 1.3.

> LogManager.GetLogger(String) is missing in .NET Standard library version
> ------------------------------------------------------------------------
> 
> Key: LOG4NET-542
> URL: https://issues.apache.org/jira/browse/LOG4NET-542
> Project: Log4net
> Issue Type: Wish
> Affects Versions: 2.0.7
> Reporter: Alexey Subach
> Priority: Critical
> 
> Hello,
> Thanks you for bringing the library to .NET Standard!
> I have a question on why LogManager.GetLogger(String) API is missing in .NET \
> Standard version but present in the .NET old fashioned one? Is there any reason for \
> that and plans to fix it? Same question for LogManager.GetRepository()
> Thanks



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[prev in list] [next in list] [prev in thread] [next in thread]