[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-392.
------------------------------------
Resolution: Invalid
This is "invalid" as we don't control the nuget package.
See also
http://blog.cincura.net/233419-log4net-nuget-package-updated-without-some-goodies/
and https://github.com/cincuranet/log4net-nuget
If the issue persists, I'd encourage you to open an issue at github
> 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: nuget, 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)
