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 "Richard J Foster (JIRA)" <ji...@apache.org> on 2007/10/09 16:55:50 UTC

[jira] Updated: (LOG4NET-123) [PATCH] EnvironmentPatternConverter does not expand User or System level environment variables under Windows

     [ https://issues.apache.org/jira/browse/LOG4NET-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard J Foster updated LOG4NET-123:
-------------------------------------

    Attachment: EnvironmentPatchAndTests.patch

I have only tested this under .NET 1.1 and 2.0, but with a bit of luck it should be good for other environments also.

> [PATCH] EnvironmentPatternConverter does not expand User or System level environment variables under Windows
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-123
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-123
>             Project: Log4net
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: 1.2.10
>         Environment: WIndows XP / WIndows 2000. .NET 2.0
>            Reporter: Richard J Foster
>            Priority: Minor
>         Attachments: EnvironmentPatchAndTests.patch
>
>
> Under .NET 2.0, there is an additional option on the System.Environment.GetEnvironment method allowing specification of a process level, user level, or machine level environment variable. If not specified, only process level environment variables will be examined.
> The attached patch enhances the EnvironmentPatternConverter. If the specified environment property is not found in the current process environment, the user environment settings will be checked. If the property is still not found, the machine level environment settings will also be tested.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.