You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Stefan Bodewig (JIRA)" <ji...@apache.org> on 2013/10/01 17:33:23 UTC
[jira] [Commented] (LOG4NET-392) Updating causing Config issue
[ https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783055#comment-13783055 ]
Stefan Bodewig commented on LOG4NET-392:
----------------------------------------
we don't build/provide NuGet packages and TBH I don't have any idea who has created the existing ones.
> 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)