Secret ingredients to quality software


Do you generate the VS Dependency Graph?

Last updated by Christian Morford-Waite [SSW] on 26 Feb 2021 01:16 am (4 months ago) See History

Dependency graphs are important because they give you an indication of the coupling between the different components within your application.

A well architected application (ie. one that correctly follows the Onion Architecture) will be easy to maintain because it is loosely coupled.

Figure: Bad Example- The Visual Studio Dependency Graph is hard to read

TimePRODependence good
Figure: Good Example – The ReSharper Dependency graph groups dependencies based on Solution Folders. By having a Consistent Solution Structure it is easy to see from your Dependency Graph if there is coupling between your UI and your Dependencies

Further Reading:

Adam CoganAdam Cogan
Adam StephensenAdam Stephensen
Igor GoldobinIgor Goldobin

We open source. This page is on GitHub