[
https://issues.apache.org/jira/browse/LOG4NET-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-395.
-----------------------------------
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
> 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)
