[
https://issues.apache.org/jira/browse/LOG4NET-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789033#comment-13789033
]
Peter Murphy commented on LOG4NET-395:
--------------------------------------
I signed up just to report on the issue.
I have been using version 2.0.1 of NuGet's packaging of Log4Net happily - that
is tied to version 1.2.12 of your release. It logs to console and files - as I
wanted.
Now the people that are maintaining the NuGet version of Log4Net have slipped
in a new version 2.0.2. This seems to be redundant, since that's also tied to
1.2.12. Moreover, it seems to have "broken" the code. I can log to a file with
2.0.1, but when I upgrade to 2.0.2, the file logging code now doesn't work.
I don't know who to complain to about it. Does anyone know?
> Nuget packaging problem - Creates app.config file in ALL projects when
> applying package.
> ----------------------------------------------------------------------------------------
>
> Key: LOG4NET-395
> URL: https://issues.apache.org/jira/browse/LOG4NET-395
> Project: Log4net
> Issue Type: Bug
> Components: Builds
> Affects Versions: 1.2.9, 1.2.10, 1.2.12
> Reporter: Adam Lith
>
> When installing (or updating!) the log4net nuget package it either:
> * Adds an app.config file if none exists
> * Transforms the app.config file if one exists.
> And it does this to all the projects that you apply the package to (as always
> with nuget).
> This is incredibly annoying because then I have to manually delete the config
> files or revert the transformations.
> The common practice for nuget-packaging is to not perform zero transforms or
> content-type additions and instead supply a link in the description of the
> package to a tutorial for those that don's know how to get started.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
