On. NET Circular Reference

In an era of increasing development patterns and widespread frameworks, more and more people rely on the development of the inherent framework pattern and ignore the understanding of the underlying architecture of the project. So when you deploy the project structure, you will encounter a "circular reference" problem that I encountered today.

In fact, it's not complicated, I have 5 projects a,b,c,d,e, and then I reference the Class B in Project A, and then I reference the class of C in B, and then I refer to the class in C, which makes a circular reference.

How can we solve this problem?

Solution One:

We consider creating a new project Z and then adding a reference to the a,b,c separately so that a,b,c just references Z.

Solution Two:

You can also create a class library project and then a,b,c,d,e,f ... The classes that need to be referenced are put into this class library project, and then all references to the class library project are OK.

In fact, the above two solutions have the same place, that is, by creating a "third party" project to do a bridge, consolidate the need to share the class, and then reference it together.

In short, or in the actual project to experience, to feel!