NuGet pack does not contain dependent packages (instead of referencing the project's DLL, which differs from includereferencedprojects)

Excluding development dependencies when creating packages

Some NuGet Packages is useful as development dependencies, which help you author your own library, but aren ' t necessarily Needed as actual package dependencies. Some examples is code-based packages or tooling packages that don ' t provide assemblies your package needs to reference at Runtime. Starting from version 2.7, the pack command would ignore <package> entries in the Packages.config file which has an Attribute developmentdependency set to true and would not include this package as a dependency in the CRE Ated package. For example, consider the following packages.config file in the source project:

<?xml version="1.0" encoding="utf-8"?><packages>    <package id="jQuery" version="1.5.2" />    developmentDependency="true" />    <package id="microsoft-web-helpers" version="1.15" /></packages>

When running-The pack command on this project, the created package would have a dependency on jQuery and Micro Soft-web-helpers, but would not have the dependency on netfx-guard.

NuGet pack does not contain dependent packages (instead of referencing the project's DLL, which differs from includereferencedprojects)