[ 
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783079#comment-13783079
 ] 

Mark Strandness commented on LOG4NET-392:
-----------------------------------------

NuGet is through the Microsoft tools.... and then it makes the link to Apache 
for the download. Here is the Description:

"The Apache Software Foundation log4net Logging Framework built from svn 
revision 1179523 of 
https://svn.apache.org/repos/asf/logging/log4net/tags/1.2.11RC1";

I removed myself from the 1.2.12 version and went back to the 1.2.11 thinking 
that it was in the new revision, but found the issue in my app.config file 
generated through the update. If you do not do the conversion/updates and you 
do not generate the xml file, then please move this on to Microsoft and have 
them take a look at it. This is an issue because another developer upgraded the 
same and got the same issue. Seems it is a repeating issue. I you don't want to 
fix, then post a notice to all out there so that they don't have to spend a 
whole day fixing this little issue. If nothing else, this is an issue, and I 
really don't care what you do or don't do, but let others know of this issue.



> Updating causing Config issue
> -----------------------------
>
>                 Key: LOG4NET-392
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-392
>             Project: Log4net
>          Issue Type: Bug
>          Components: Builds
>    Affects Versions: 1.2.12
>         Environment: Windows 7 (64 bit) using Visual Studio 2012, NHibernate, 
> and Postgres
>            Reporter: Mark Strandness
>              Labels: patch
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> I did an update yesterday from the VS 2012 NuGet Manager and afterwards, keep 
> getting a Configuration.Cfg error on my NHibernate. Found where you have 
> changed the log4net config and it added a second config for the log4net 
> package. 
> <configuration>
>   <configSections>
>     <section name="log4net"                                                   
> \/ type="log4net.Config.Log4NetConfigurationSectionHandler,Log4net" />
>     <section name="log4net"                                                   
>   type="log4net.Config.Log4NetConfigurationSectionHandler, log4net" />
>   </configSections>                                                           
>       /\
> I commented out the bottom line and I now have an operational system again. 
> Small error but for the size of this system, very time consumming. Almost 
> ripped out all the log4net system to go elsewhere, but I saved it..
> Make your update soon before many other people have this same issue.



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

Reply via email to