logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominik Psenner (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4NET-406) Log4Net breaks the Microsoft naming rules for namespaces
Date Wed, 20 Nov 2013 12:55:35 GMT

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

Dominik Psenner updated LOG4NET-406:
------------------------------------

    Fix Version/s: 1.3.0

> Log4Net breaks the Microsoft naming rules for namespaces
> --------------------------------------------------------
>
>                 Key: LOG4NET-406
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-406
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Appenders, Core
>    Affects Versions: 1.2.9, 1.2.10, 1.2.11, 1.2.12, 1.2.13, 1.3.0, 1.2 Maintenance Release,
3.5, 4.0
>         Environment: Windows 7, .Net 4.0
>            Reporter: Michael Goldfinger
>            Priority: Trivial
>             Fix For: 1.3.0
>
>
> The log4net namespace violates the naming convention for namespaces in .Net.
> http://msdn.microsoft.com/en-us/library/vstudio/ms229026(v=vs.100).aspx
> As stated Pacal casing should be used: "Do use Pascal casing, and separate namespace
components with periods (for example, Microsoft.Office.PowerPoint)"



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

Mime
View raw message