Implementation of the Visual Studio 2013 package visualizer as a Visual Studio 2015 extension. Version for VS 2017 can be found here: https://github.com/brentkrueger/VisualStudio2017PackageVisualizer
I have been migrating my team's apps from net40 to net462.
We use LinqKit and Microsoft.AspNet.WebApi.Client. When targeting net40, these have additional dependencies on packages which backport .Net 4.5 features:
Microsoft.Net.Http
Microsoft.BCL, BCL.Build and BCL.Async
The tool should detect the target framework of each project and either omit or visually differentiate edges representing dependencies which don't apply under the current target(s).
This is particularly valuable since referencing these in a class library forces consuming projects to also have them referenced.
I have been migrating my team's apps from net40 to net462.
We use LinqKit and Microsoft.AspNet.WebApi.Client. When targeting net40, these have additional dependencies on packages which backport .Net 4.5 features: Microsoft.Net.Http Microsoft.BCL, BCL.Build and BCL.Async
The tool should detect the target framework of each project and either omit or visually differentiate edges representing dependencies which don't apply under the current target(s).
This is particularly valuable since referencing these in a class library forces consuming projects to also have them referenced.