The default behavior of nuget pack is great when its called against a csproj. It will look at the corresponding nuspec and packages.config files and it will automatically include dependencies.
However, not all dependencies are runtime dependencies. Some dependencies are build-time tools type dependencies.
I don't see a convenient means of excluding a package dependency that doesn't need to ship with the resulting nupkg file.
I would like to see this added as a feature. A simple means of excluding dependencies in the .nuspec file would suffice.
Comments: Most of it. However, we detected two important issues: [https://nuget.codeplex.com/workitem/3378](https://nuget.codeplex.com/workitem/3378) [https://nuget.codeplex.com/workitem/3375](https://nuget.codeplex.com/workitem/3375) Other minor issues were detected, but they are more related to the user experience: [https://nuget.codeplex.com/workitem/3383](https://nuget.codeplex.com/workitem/3383) [https://nuget.codeplex.com/workitem/3382](https://nuget.codeplex.com/workitem/3382) Overall the quality is good.
However, not all dependencies are runtime dependencies. Some dependencies are build-time tools type dependencies.
I don't see a convenient means of excluding a package dependency that doesn't need to ship with the resulting nupkg file.
I would like to see this added as a feature. A simple means of excluding dependencies in the .nuspec file would suffice.
Comments: Most of it. However, we detected two important issues: [https://nuget.codeplex.com/workitem/3378](https://nuget.codeplex.com/workitem/3378) [https://nuget.codeplex.com/workitem/3375](https://nuget.codeplex.com/workitem/3375) Other minor issues were detected, but they are more related to the user experience: [https://nuget.codeplex.com/workitem/3383](https://nuget.codeplex.com/workitem/3383) [https://nuget.codeplex.com/workitem/3382](https://nuget.codeplex.com/workitem/3382) Overall the quality is good.