[
https://issues.apache.org/jira/browse/LOG4NET-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831054#comment-13831054
]
Stefan Bodewig commented on LOG4NET-406:
----------------------------------------
I'm really on the fence here, but the guideline says
bq. If your brand employs nontraditional casing, you should follow the casing
defined by your brand, even if it deviates from normal namespace casing
The official brand is "Apache log4net" with an all lowercase log4net.
> 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)
