[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789289#comment-13789289
]
Mark Strandness commented on LOG4NET-392:
-----------------------------------------
Fine... you doing it for FREE.. I acknowledge that... but if a bug is
introduced by your program... it need to be addressed... not brushed off as
INVALID...
Microsoft is REAL INTERESTED IN YOUR RESPONSES. I hope in the future you don't
have to do it for FREE because you will not be included in the available
packages . I have removed your logging system and will write my own since your
stupid reply this morning... Thanks for making my day longer... This is going
out to thousands of my customers and I will not accept stupidity from someone
that wants people to use their software and not stand behind and resolve an
issue, NO MATTER WHO is at fault. If NuGet can't fix the issue, I bet you blame
the janitor who cleans your shitters next, huh
> Updating causing Config issue
> -----------------------------
>
> Key: LOG4NET-392
> URL: https://issues.apache.org/jira/browse/LOG4NET-392
> Project: Log4net
> Issue Type: Bug
> 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)
