You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Dominik Psenner (JIRA)" <ji...@apache.org> on 2013/10/03 15:06:42 UTC
[jira] [Closed] (LOG4NET-395) Nuget packaging problem - Creates
app.config file in ALL projects when applying package.
[ https://issues.apache.org/jira/browse/LOG4NET-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominik Psenner closed LOG4NET-395.
-----------------------------------
Resolution: Duplicate
This looks like being a duplicate of LOG4NET-392. Feel free to reopen the issue if that's not the case.
However, please notice that we do not build/provide NuGet packages and you should contact the package maintainer about this issue, maybe with a link to this issue and LOG4NET-392.
> 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)