[jira] [Assigned] (LOG4NET-132) Environment variables are mistakenly case sensitive on windows

["Stefan Bodewig (JIRA)" <ji...@apache.org>]

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

Stefan Bodewig reassigned LOG4NET-132:
--------------------------------------

    Assignee: Stefan Bodewig

> Environment variables are mistakenly case sensitive on windows
> --------------------------------------------------------------
>
>                 Key: LOG4NET-132
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-132
>             Project: Log4net
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.10
>         Environment: Windows, .Net 3.5
>            Reporter: Matthew Gabeler-Lee
>            Assignee: Stefan Bodewig
>            Priority: Minor
>             Fix For: 1.2.13
>
>
> On windows, environment variables are meant to be case insensitive.  Because of this, in some contexts, a special IDictionary class that lowercases all the keys is used to manipulate environment variables, specifically ProcessStartInfo.EnvironmentVariables.
> The upshot of this, for me, is that when running under the profiler I have, all the environment variables get lowercased, and my logging configuration is broken, because TEMP is now temp, and log4net is treating the environment variables in a case sensitive manner, from using Environment.GetEnvironmentVariables(), which creates a normal case sensitive Hashtable object.
> It seems that, on windows, the result of Environment.GetEnvironmentVariables() should be copied into a StringDictionary to get proper case insensitive behavior.



--
This message was sent by Atlassian JIRA
(v6.1#6144)