Do you generate the VS Dependency Graph?
30/06/2014 9:54 PM by
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
- 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
Do you feel this rule needs an update?