To see the artifacts that are linked to a layer, open the shortcut menu for the layer, and then choose View Links to open Layer Explorer.įor more information, see Layer Explorer. These artifacts can be namespaces, projects, classes, methods, and so on. ShapeĪ logical group of physical artifacts in your system. The following table describes the elements that you can use on a dependency diagram. For more information about layering patterns, visit the Patterns & Practices site.

For more detailed information about how to create and draw dependency diagrams, see Dependency Diagrams: Guidelines. This topic describes the elements that you can use on a dependency diagram. Reinforce the intended architecture during the development and maintenance of your code by including validation with your check-in and build operations. Visualize the impact of changes on the intended architecture when you refactor, update, or evolve your system.

Use a dependency diagram to help you perform the following tasks:Ĭommunicate the existing or intended logical architecture of your system.ĭiscover conflicts between your existing code and the intended architecture. By organizing your system into layers that describe distinct roles and functions, a dependency diagram can help make it easier for you to understand, reuse, and maintain your code. These dependencies, which are represented as arrows, indicate which layers can use or currently use the functionality represented by other layers. You can specify the intended or existing dependencies between layers. NET Core projects are supported starting in Visual Studio 2019 version 16.2.

Visual studio marketplace free graph