Since TFS builds all binaries to the same folder, the nuspec file (without the element) takes all binaries, copies them to the NuGet-temp folder, and packages them into each nupkg file.
Is there a way to get around this? I want each packaged project, and its assembly dependencies, in a nupkg file.
I had the same problem while testing Octopusdeploy in my company. The package created by Octopack for EXE projects contains every single file of build drop folder.
The way I found to solve this was changing the build workflow, using the solution proposed in this article:
The only issue is you need a separated solution for each EXE project, but in a single build definition you can build multiple solutions.
I also personalized the build definition to call Octo.exe after the build and create a new release with lastests packages. And I have made a fork in Octo.exe project and changed it to allow passing “generic” versions numbers, described here:
This allows to the release version automatically be incremented in every build on TFS.
Thanks for PublishedApplications package reference.
I’ve installed the package: http://www.nuget.org/packages/PublishedApplications for each Executable in My Solution and it created subfolders for each project.