Could not get dependencies for project reference validating website dating adds of women with height and weight
The old issues have an error code starting with AV (Architecture Validation errors) whereas the new issues have an error code starting with DV (Dependency Validation errors).
To be fair, you might not notice these differences, however, there is a case where you will.
This issue is reported on a code element associated with a layer which “Allowed Namespace Names” property does not contain the namespace in which this code element is defined. Note that the syntax of “Allowed Namespace Names” is to be a semi-colon list of namespaces in which code elements associated with are layer are permitted to be defined. 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 Disallowed namespace name.
This issue is reported on a code element associated with a layer which “Disallowed Namespace Names” property contains the namespace in which this code element is defined. Note that the “Disallowed namespace name” property is defined as a Semi-colon separated list of namespaces in which code elements associated with this Layer should not be defined.
Navigate to Architecture – “Generate Code Map for Solution” This will generated the nice dependency diagram for the projects.
As shown in the below images, you can see how the projects / libraries are dependent on each other in a single view.
Finally, I describe how users using the current experience can migrate to the new one I encourage you to watch this 10 mins video, which will give you a good overview of the scenario and the feature.
In the same way that you sometimes must add a reference to an assembly declaring a base interface for a class you use (whereas you don’t yourself reference this base interface), the compiler sometimes generates constructs which are not effectively used, but were drawing a dependency in binary, which is not visible in source code.
So, the binary caught legacy validation issues which logically should not be there, whereas the new real time dependency validation won’t. (One case I met is when calling a method passing as a parameter a delegate which had an offending return type).
Select the project from the “Projects” dropdown to see the related dependent projects As shown in the above pictures all the dependent projects are “ from the context menu, and then select Project Dependencies.
You can also visualize the dependency of projects using Code Map and I personally prefer this options.
As we have explained last month, the Dependency Validation experience leverages the existing Layer diagram format with some improved terminology for the layer properties.