Issue with publishing non-reference DLLs

Topics: General
Oct 1, 2013 at 6:12 PM
Edited Oct 1, 2013 at 6:13 PM
I just got a project dumped on me that is a pretty simple ASP.NET application with a number of DLLs as dependencies. In particular, I've created a NuGet package for 4 of these DLLs because they're all required as part of the API being used. Only one of them needs to be added as a reference though, the other 3 are referenced by the first one.

However, when I do a build or publish only 2 of the 4 DLLs get output to the bin folder...the referenced DLL and 1 of 3 of the others. All 4 are listed in the NuGet package, with the referenced DLL under \lib\net and the other non-referenced DLLs under \content\bin. It's always the same 2 that don't get copied but there's nothing unique about them in the package that I've created with the Package Explorer GUI.

I've tried recreating the package, uninstalling/reinstalling the package, etc and it still occurs. Has anyone seen this before or have some suggestions as a better way to add non-referenced DLLs that still need to go into \bin?