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 "Adam Lith (JIRA)" <ji...@apache.org> on 2013/10/03 14:56:43 UTC
[jira] [Created] (LOG4NET-395) Nuget packaging problem - Creates
app.config file in ALL projects when applying package.
Adam Lith created LOG4NET-395:
---------------------------------
Summary: 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.12, 1.2.10, 1.2.9
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)