Comments (12)
The issue is here https://github.com/glennc/dotnet-packages/blob/master/PackagesCommand.cs#L103
dependency.VersionRange
is null
from dotnet-packages.
Makes sense, need to check for that type of dependency and write something else out.
from dotnet-packages.
Could we get the dependencies on that project and write it's dependencies
out however that project may also depend on another project so you'd have
to decide how many recursive projects you'd support I guess
On Sunday, 14 August 2016, Glenn Condron [email protected] wrote:
Makes sense, need to check for that type of dependency and write something
else out.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#2 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGapv0awGipjsLKLzJM-J6mD0lxBW5Mks5qf5ftgaJpZM4Jgav-
.
from dotnet-packages.
And indent each level or something? Do you think it would be understandable enough?
from dotnet-packages.
Also, just realized I am not showing target anywhere in the information. Since it wasn't a concept when I first put it together.
from dotnet-packages.
Yeah not sure how we'd do the UI for nesters deps but I think it needs
doing :)
On Sunday, 14 August 2016, Glenn Condron [email protected] wrote:
Also, just realized I am not showing target anywhere in the information.
Since it wasn't a concept when I first put it together.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#2 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGapkhruirAk5V9wONGxzs-vMzGkbLrks5qf5uFgaJpZM4Jgav-
.
from dotnet-packages.
What about to begin with we do an extra block for each project dependency that appears? Something like this:
λ dotnet packages
test2 Dependency Information
Framework: .NETStandard1.6
--------------------------------------------------------------------------------------------------------------
DependencyName | Type | Requested Version | Resolved Version
--------------------------------------------------------------------------------------------------------------
NETStandard.Library | default | 1.6.0 | 1.6.0
test1 | default | | 1.0.0
test1 Dependency Information
Framework: .NETStandard1.6
--------------------------------------------------------------------------------------------------------------
DependencyName | Type | Requested Version | Resolved Version
--------------------------------------------------------------------------------------------------------------
NETStandard.Library | default | 1.6.0 | 1.6.0
Diagnostics
Error
--------------------------------------------------------------------------------------------------------------
NONE
--------------------------------------------------------------------------------------------------------------
Warning
--------------------------------------------------------------------------------------------------------------
NONE
--------------------------------------------------------------------------------------------------------------
Info
--------------------------------------------------------------------------------------------------------------
NONE
--------------------------------------------------------------------------------------------------------------
Configured NuGet Feeds:
--------------------------------------------------------------------------------------------------------------
Feed | From Config
--------------------------------------------------------------------------------------------------------------
https://www.nuget.org/api/v2/ | C:\Users\Glenn\AppData\Roaming\NuGet\NuGet.Config
http://www.myget.org/F/aspnetvnext | C:\Users\Glenn\AppData\Roaming\NuGet\NuGet.Config
http://www.myget.org/F/aspnetwebstacknightly/ | C:\Users\Glenn\AppData\Roaming\NuGet\NuGet.Config
from dotnet-packages.
*nested
On Sunday, 14 August 2016, Jonathan Channon [email protected]
wrote:
Yeah not sure how we'd do the UI for nesters deps but I think it needs
doing :)On Sunday, 14 August 2016, Glenn Condron <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:Also, just realized I am not showing target anywhere in the information.
Since it wasn't a concept when I first put it together.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#2 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGapkhruirAk5V9wONGxzs-vMzGkbLrks5qf5uFgaJpZM4Jgav-
.
from dotnet-packages.
Yup good call.
I think what we need to show is if projA depends on orojB that depends on
json.net that we can see graph
On Sunday, 14 August 2016, Jonathan Channon [email protected]
wrote:
*nested
On Sunday, 14 August 2016, Jonathan Channon <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:Yeah not sure how we'd do the UI for nesters deps but I think it needs
doing :)On Sunday, 14 August 2016, Glenn Condron [email protected]
wrote:Also, just realized I am not showing target anywhere in the information.
Since it wasn't a concept when I first put it together.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#2 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGapkhruirAk5V9wONGxzs-vMzGkbLrks5qf5uFgaJpZM4Jgav-
.
from dotnet-packages.
It probably only helps with top level dependencies in the suggested form, but it would be better than nothing to begin with, I think.
from dotnet-packages.
If you know that you are interested in json.net, then you can find out what you are after by doing dotnet packages json
. In my case I have test2 that depends on test1 that depends on json.net, the output of dotnet packages json
is this:
λ dotnet packages json
test2 Dependency Information
Framework: .NETStandard1.6
------------------------------------------------------------------------------------------------------------------------
Dependency: Newtonsoft.Json
Type: Package
Selected Version: 9.0.1
Expected Location: C:\Users\Glenn\.nuget\packages\Newtonsoft.Json\9.0.1
Resolved: Γ£ô
Depended on by:
----------------------------------------------------------------------------------------------------
Top Level | Parent | Requested Version
----------------------------------------------------------------------------------------------------
* | test1 | 9.0.1
-----------------------------------------------------------------------------------------------
Depends on:
-----------------------------------------------------------------------------------------------
Dependency | Version | Resolved
-----------------------------------------------------------------------------------------------
Microsoft.CSharp | 4.0.1 | Γ£ô
System.Collections | 4.0.11 | Γ£ô
System.Diagnostics.Debug | 4.0.11 | Γ£ô
System.Dynamic.Runtime | 4.0.11 | Γ£ô
System.Globalization | 4.0.11 | Γ£ô
System.IO | 4.1.0 | Γ£ô
System.Linq | 4.1.0 | Γ£ô
System.Linq.Expressions | 4.1.0 | Γ£ô
System.ObjectModel | 4.0.12 | Γ£ô
System.Reflection | 4.1.0 | Γ£ô
System.Reflection.Extensions | 4.0.1 | Γ£ô
System.Resources.ResourceManager | 4.0.1 | Γ£ô
System.Runtime | 4.1.0 | Γ£ô
System.Runtime.Extensions | 4.1.0 | Γ£ô
System.Runtime.Serialization.Primitives | 4.1.1 | Γ£ô
System.Text.Encoding | 4.0.11 | Γ£ô
System.Text.Encoding.Extensions | 4.0.11 | Γ£ô
System.Text.RegularExpressions | 4.1.0 | Γ£ô
System.Threading | 4.0.11 | Γ£ô
System.Threading.Tasks | 4.0.11 | Γ£ô
System.Xml.ReaderWriter | 4.0.11 | Γ£ô
System.Xml.XDocument | 4.0.11 | Γ£ô
-----------------------------------------------------------------------------------------------
Which shows you that json.net was pulled in as a top level package dependency by test1. Of course, it doesn't immediately help with how test1 got into the graph...
from dotnet-packages.
Nice!!
On Monday, 15 August 2016, Glenn Condron [email protected] wrote:
If you know that you are interested in json.net, then you can find out
what you are after by doing dotnet packages json. In my case I have test2
that depends on test1 that depends on json.net, the output of dotnet
packages json is this:λ dotnet packages json
test2 Dependency InformationFramework: .NETStandard1.6
Dependency: Newtonsoft.Json
Type: Package
Selected Version: 9.0.1
Expected Location: C:\Users\Glenn.nuget\packages\Newtonsoft.Json\9.0.1
Resolved: Γ£ôDepended on by:
Top Level | Parent | Requested Version
* | test1 | 9.0.1
Depends on:
Dependency | Version | Resolved
Microsoft.CSharp | 4.0.1 | Γ£ô
System.Collections | 4.0.11 | Γ£ô
System.Diagnostics.Debug | 4.0.11 | Γ£ô
System.Dynamic.Runtime | 4.0.11 | Γ£ô
System.Globalization | 4.0.11 | Γ£ô
System.IO | 4.1.0 | Γ£ô
System.Linq | 4.1.0 | Γ£ô
System.Linq.Expressions | 4.1.0 | Γ£ô
System.ObjectModel | 4.0.12 | Γ£ô
System.Reflection | 4.1.0 | Γ£ô
System.Reflection.Extensions | 4.0.1 | Γ£ô
System.Resources.ResourceManager | 4.0.1 | Γ£ô
System.Runtime | 4.1.0 | Γ£ô
System.Runtime.Extensions | 4.1.0 | Γ£ô
System.Runtime.Serialization.Primitives | 4.1.1 | Γ£ô
System.Text.Encoding | 4.0.11 | Γ£ô
System.Text.Encoding.Extensions | 4.0.11 | Γ£ô
System.Text.RegularExpressions | 4.1.0 | Γ£ô
System.Threading | 4.0.11 | Γ£ô
System.Threading.Tasks | 4.0.11 | Γ£ô
System.Xml.ReaderWriter | 4.0.11 | Γ£ôSystem.Xml.XDocument | 4.0.11 | Γ£ô
Which shows you that json.net was pulled in as a top level package
dependency by test1. Of course, it doesn't immediately help with how test1
got into the graph...—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#2 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGapqA-nHE88kH6_Hve5NBNcCuUjeAnks5qf6EMgaJpZM4Jgav-
.
from dotnet-packages.
Related Issues (2)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dotnet-packages.