This project is read-only.
1

Closed

Pack command for .csproj file doesn't add dependencies when targeting multiple frameworks

description

There is a bug pulling in dependencies when targeting multiple frameworks using the "nuget pack" command on a .csproj file. It attempts to add the packages multiple times and fails with an "Item already exists" exception.

Discussion began here: https://nuget.codeplex.com/discussions/441303

It turns out this has nothing to do with dependencies, but it had to do with the XML documentation files. The "nuget pack" command was attempting to add both Assembly.xml and Assembly.XML to the package and that's what was eventually causing the "Item already exists" exception.
Closed Jul 18, 2013 at 10:46 PM by deepakverma

comments

dotnetjunky wrote Apr 27, 2013 at 4:05 AM

Good catch. Will look at your request.

dotnetjunky wrote May 3, 2013 at 10:21 PM

Fixed in changeset 2dd930579ae4064192a9422c284a2de7286c353d