[
https://issues.apache.org/jira/browse/LOG4NET-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288113#comment-13288113
]
Stefan Bodewig commented on LOG4NET-321:
----------------------------------------
Yes, I think this could be modelled like the
log4net.Layout.Pattern.PropertyPatternConverter and the way it is integrated.
One thing to keep in mind would be that we still haven't formally dropped 1.x
support so there have two be some conditional compiles to deal with the
different APIs used when accessing appsettings.
> Add AppSettings lookup to configuration reader value setting
> ------------------------------------------------------------
>
> Key: LOG4NET-321
> URL: https://issues.apache.org/jira/browse/LOG4NET-321
> Project: Log4net
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.2.11
> Reporter: Jonathan Choy
> Priority: Minor
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Add wrapper lookup to resolve AppSetting key/value pairs in the same fashion
> as environment variables during configuration. This facilitates deploying the
> same codebase across environments where the logging configuration differs
> only by a machine-specific key/value pair that would already be stored,
> forex, in the machine.config or a per-server or per-environment local
> web.config transform, and the transform is applicable but setting environment
> variables is not. (AppHarbor style hosting, for a specific example).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
