Nuget install command for explicit packages.config, why does it ignore dependencies?

Oct 26, 2011 at 11:31 PM

Curious why the install command when used against a packages.config file chooses to ignore dependencies. In our new project structure we are combining the contents of all the packages.config files in various projects that belong to a solution and putting them into a single packages.config file at the root of our solution and when we run the nuget.exe install against that packages.config we would like it to resolve all dependencies for those packages as well.

Due to how the nuget.exe works at the moment, we are using our executable that uses the Nuget.Core api directly to accomplish this. Any objections to changing this?

Oct 27, 2011 at 12:35 AM

We expect packages.config to have the full closure of all installed packages. We ignore looking up dependencies since we know we are going to install the dependency either which way.

In your case, the merged config file should also have it unless you're excluding them.

Oct 27, 2011 at 4:07 AM

This came up before. See this issue.