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

Stefan Bodewig updated LOG4NET-292:
-----------------------------------

    Affects Version/s:     (was: 1.2.10)
                       1.2.11
        Fix Version/s:     (was: 1.2 Maintenance Release)
                       1.2.12

I've renamed the class and made it compile on .NET 2.0 (automatic Has*Color 
properties in LevelColors).  Other than that the code is in with svn revision 
1197200.

Do you think you could provide a small documentation snippet for 
http://logging.apache.org/log4net/release/config-examples.html which is based 
on 
https://svn.apache.org/repos/asf/logging/log4net/trunk/src/site/xdoc/release/config-examples.xml
 ?
                
> Managed ColoredConsoleAppender for .NET2/Mono.
> ----------------------------------------------
>
>                 Key: LOG4NET-292
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-292
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 1.2.11
>            Reporter: Pavlos Touboulidis
>            Priority: Minor
>             Fix For: 1.2.12
>
>         Attachments: ColoredConsoleAppender2.cs
>
>
> The original ColoredConsoleAppender was written before the .NET framework 
> (and Mono) had built-in support for console colors so it was written using 
> Win32 API calls. The AnsiColorTerminalAppender, while it works, isn't 
> understood by the Windows command prompt so there's no console appender that 
> works on both environments.
> I'm attaching a replacement for both classes that uses the new (.NET 2) 
> console colors and works on both platforms. It is based on the existing 
> ColoredConsoleAppender. The color mapping values are not compatible with the 
> previous version since this one uses the standard .NET 2 ConsoleColor 
> enumeration values.

--
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

        

Reply via email to