[
https://issues.apache.org/jira/browse/LOG4NET-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827613#comment-13827613
]
Dominik Psenner edited comment on LOG4NET-406 at 11/20/13 1:05 PM:
-------------------------------------------------------------------
This is a API breaking change and we may fix it with 1.3.0. However, due to the
fact that log4net is a port of log4j, both share the namespaces even though
this breaks the .NET naming conventions and changing this may produce
confusion. On top of that it will result in a lot of work for people who
migrate from 1.2.X to 1.3.0 cause people will have to fix their
"using"-directives manually.
was (Author: nachbarslumpi):
This is a API breaking change and we may fix it with 1.3.0. However, due to the
fact that log4net is a port of log4j, both share the namespaces even though
this breaks the .NET naming conventions.
> 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)
