[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789256#comment-13789256
]
Mark Strandness commented on LOG4NET-392:
-----------------------------------------
That's fine... PLEASE REMOVE the "INVALID" as this issue has been" VALIDATED" .
Just replace the INVALID to "can't fix because we don't give a damn"...
I guess you'll get more of this issue from others because you don't care, but
make it so that others do see the issue and know that it is an issue and there
is a solution to it and not have to spend hours tracking it down. That would be
nice. I looked on your site and there was nothing reported. Made the report and
now you want to sweep under the rug. Are you too lazy to contact NuGet to find
the issue and repair this bug? Can't you people work together?
Thanks for building my faith in a MAJOR issue becoming someone else's issue. I
bet you've been doing that for so many years, it just makes you feel
comfortable. Typical developer... it's not my issue, it is the next person down
the line... Make me feel good about using your software. I will be looking
elsewhere for other software so not to have an issue with you in the future...
WHEW... glad I found out NOW how worthless you are!
On to extraview.com to report your issue that you claim is INVALID and make a
bigger stink out there on you... maybe drive your product into the ground. Also
on to Microsoft and let them know how un-compatible you are to their software
and blame you for the issue in your software. Maybe they even knock you off
your pedestal and find a better logger. Wait til they hear about you
introducing errors and CREATING an invalid bug into their software. Wonder if
Microsoft reported this to you already and you IGNORED them also????
Good Luck in the future... what you have left of it... KMA
> 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)
