Skip to content
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.

Clearly indicate where dependencies are resolved from in build output #305

Closed
halter73 opened this issue Jun 10, 2014 · 2 comments
Closed

Comments

@halter73
Copy link
Member

When I modify global.json and run build.cmd, it is unclear whether dependencies are picked up from the new sources referenced in global.json or from nuget.

@davidfowl davidfowl modified the milestones: 1.0.0-alpha2, 1.0.0-alpha3 Jun 24, 2014
@davidfowl davidfowl self-assigned this Jun 24, 2014
@davidfowl davidfowl modified the milestones: 1.0.0-beta1, 1.0.0-alpha4 Sep 8, 2014
@glennc glennc assigned ChengTian and unassigned davidfowl Oct 7, 2014
@glennc
Copy link
Member

glennc commented Oct 7, 2014

@ChengTian This is similar to what KPM pack does. Write out all the dependencies in the dependency graph and where we loaded them from. It should be displayed by default and turned off by passing --quiet

We should make pack and build the same, the output could be something like this:

Using {Assembly|Package|Project} dependency {id} {version} for {targetFramework}
  Source: {source path}
  Target: {target path} (when doing kpm pack)
  File: {lib\aspnet50\x.dll} (when appropriate)

@ChengTian
Copy link
Contributor

This issue depends on @pranavkm 's change at #699

I'll work on it after that change is checked in.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants