For more information about validation errors, see Understand and resolve layer validation errors.
During the development process, you might want to suppress some of the reported conflicts during validation.
Video: Validate your architecture dependencies in real time To make sure that code doesn't conflict with its design, validate your code with dependency diagrams in Visual Studio.
This can help you: To see which versions of Visual Studio support this feature, see Version support for architecture and modeling tools.
When you run validation the next time, these errors will not appear.
Suppressed errors are tracked in a .suppressions file for the corresponding dependency diagram file.
This issue is reported on a code element associated with a layer and referencing another code element defined in a namespace which is defined in the "Unreferenceable Namespace" property of the layer. Note that the "Unreferenceable Namespaces" property is defined as a Semi-colon separated list of namespaces that should not be referenced in code elements associated with this layer.
Such references are not considered dependencies unless the code uses those references.
To create gated check-in builds, see Use a gated check-in build process to validate changes.
The following table describes layer validation issues and their resolution.
Validation does not work on dependency diagrams that are copied from other dependency diagrams in Solution Explorer and that are in the same modeling project.
dependency diagrams that are copied in this way contain the same references as the original dependency diagram.