package dependencies

Aug 20, 2010 at 1:09 PM

From: David Fowler []
Sent: Wednesday, August 18, 2010 10:53 AM
To: Dru Sellers; David Ebbo
Cc: Simser, Bil; Phil Haack; Rob Reynolds
Subject: RE: package dependencies

Sounds like a useful thing to have. The package walker Is doing a lot of the dependency management and conflict detection right now. We should think about how we can surface that in a useful way.

From: Dru Sellers []
Sent: Wednesday, August 18, 2010 7:35 AM
To: David Ebbo
Cc: Simser, Bil; Phil Haack; David Fowler; Rob Reynolds
Subject: Re: package dependencies

One of the things that would be nice is if this was a core part of the library.
I will keep tweaking it and see what I can come up with.

On Tue, Aug 17, 2010 at 5:08 PM, David Ebbo <> wrote:

I agree it would be nice to give the user some tools that display dependency trees in a simple-to-read way.  I believe we already have code that will detect conflicts at Add-PackageReference time, but we don’t expose this through other commands.


From: Dru Sellers []
Sent: Tuesday, August 17, 2010 2:34 PM
To: Simser, Bil; Phil Haack; David Fowler; Rob Reynolds; David Ebbo
Subject: package dependencies

I was thinking, if we used QuickGraph ( we could build a pretty solid graph of all of the dependencies and then walk the graph to look for version conflicts. When we find them we can use its GLEE support to show the user a graph or render a text display in PowerShell.

I spiked it out a little bit today and looks pretty simple

Got this text output (nothing huge here, the goal would be the graphical file plus more advanced debugging support)

Contains Conflicts
    NHibernate-1.0 wants log4net-1.0
    castle-dynamicproxy-1.0 wants log4net-2.0