An error checking the validation of the VS 2010 level diagram shows that there is not even a dependency (AV0001)

Question

I get the following validation error on the layer chart:

  Error 65 AV0001: Invalid Dependency: Weld.Interface.Core (Assembly) -> Weld.Interface (Namespace)
     Layers: Application Framework Core, Application Framework |  Dependencies: Namespace Reference D: \ Projects \ Windows Projects \ Weld \ Weld \ ModelingProject1 \ Weld.layerdiagram 0 0 ModelingProject1

These 2 assemblies are configured as different layers, and the assembly name also represents the starting point of the namespace.

Weld.Interface.Core: this assembly and namespace have no reference to Weld.Interface and only references to .NET Framework classes

Weld.Interface: this assembly and namespace have no reference to Weld.Interface.Core

There is no dependence on these two levels in the dependency diagram. I am confused why I get this error. There is no dependency on the project or code, and no dependency is even set up on the layer diagram.

Somehow, the verification logic in the layer diagram sees a non-existent dependency and says that this is a mistake.

Any ideas that I might have missed, or what causes this problem?

Answer 1

Well, I realized what was happening with my situation, and thought that I would pass it on here. This seems to be the issue of cached assembly references. When the modeling project was originally created, it was in its own decision, separate from the assemblies that it intends to simulate. So he had to list them in Layer References for the Modeling project.

The project has since been included in the general solution, but I believe that links to projects originally announced when they were separated from the solution took precedence and, ultimately, referred to the old code. I removed assemblies from the Layer References of the Modeling project, after which everything was smooth.