You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Jonathan Choy (Commented) (JIRA)" <ji...@apache.org> on 2012/01/25 18:30:40 UTC

[jira] [Commented] (LOG4NET-321) Add AppSettings lookup to configuration reader value setting

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

Jonathan Choy commented on LOG4NET-321:
---------------------------------------

Suggested syntax would be in the same style as $env{value}:

$AppSetting{keyname} would retrieve the setting from ConfigurationManager.AppSetting[keyname] if present, with not-present using the same missing value semantics as $env.

Suggested semantic enhancement if not present: If in debug mode, report empty key lookup substitutions from both $env and $AppSetting.

                
> 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