[
https://issues.apache.org/jira/browse/LOG4NET-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830995#comment-13830995
]
Ben edited comment on LOG4NET-406 at 11/25/13 1:47 AM:
-------------------------------------------------------
Yes, I understand that this is an API breaking change and yes Jonathan's
comments about this being a guidance and not a hard-and-fast rule are also
valid. However I do not agree that "there is only negative value in this
proposal".
I am fairly new to log4net, and when I stated using it and found that the using
directive was all lower case letters, I found this slightly confusing and
disconcerting (did I install the right version; am I using a test version; did
I mess something up). I would have considered a renaming of the namespace an
important part of the port from log4j to .NET. If you are going to port to
.NET then you should be taking the .NET Framework Guidelines seriously, which
you probably are, but for your brand new users who aren't familiar with the 10
year namespace history, the lowercase using directive introduces uncertainty
and worry.
This was my experience. So I do not think that this proposal has only negative
value.
I would also like to point out that during a migration to a newer version there
is a Find and Replace tool within Visual Studio that can be set to scan the
entire Solution. It could be used to replace "using log4net" to "using
Log4Net" and this would be fairly painless and quick. So its not necessarily
an entirely manual operation.
While I do not expect everyone to agree with me, I don't think I am the only
one to feel this way and I do hope that my opinion is a valuable contribution
to this debate.
was (Author: benixix):
Yes, I understand that this is an API breaking change and yes Jonathan's
comments about this being a guidance and not a hard-and-fast rule are also
valid. However I do not agree that "there is only negative value in this
proposal".
I am fairly new to log4net, and when I stated using it and found that the using
directive was all lower case letters, I found this slightly confusing and
disconcerting (did I install the right version; am I using a test version; did
I mess something up). I would have considered a renaming of the namespace an
important part of the port from log4j to .NET. If you are going to port to
.NET then you should be taking the .NET Framework Guidelines seriously, which
you probably are, but for your brand new users who aren't familiar with the 10
year namespace history, the lowercase using directive make log4net look like it
has been built by amateurs and introduces uncertainty and worry.
This was my experience. So I do not think that this proposal has only negative
value.
I would also like to point out that during a migration to a newer version there
is a Find and Replace tool within Visual Studio that can be set to scan the
entire Solution. It could be used to replace "using log4net" to "using
Log4Net" and this would be fairly painless and quick. So its not necessarily
an entirely manual operation.
While I do not expect everyone to agree with me, I don't think I am the only
one to feel this way and I do hope that my opinion is a valuable contribution
to this debate.
> 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)
