Circular Dependency Solution

c# .net design-patterns architecture circular-dependency
gfoley picture gfoley · Apr 8, 2010 · Viewed 24.2k times · Source

Our current project has ran into a circular dependency issue. Our business logic assembly is using classes and static methods from our SharedLibrary assembly. The SharedLibrary contains a whole bunch of helper functions, such as a SQL Reader class, Enumerators, Global Variables, Error Handling, Logging and Validation.

The SharedLibrary needs access to the Business objects, but the Business objects need access to SharedLibrary. The old developers solved this obvious code smell by replicating the functionality of the business objects in the shared library (very anti-DRY). I've spent a day now trying to read about my options to solve this but i'm hitting a dead end.

I'm open to the idea of architecture redesign, but only as a last resort. So how can i have a Shared Helper Library which can access the business objects, with the business objects still accessing the Shared Helper Library?

Answer

Samuel Carrijo picture Samuel Carrijo · Apr 8, 2010

You could create a separate project only for value objects (no logic) and interfaces.

Have your shared library classes implement the interfaces, and the Business library depend on the interfaces (do I hear more testable and decoupled code here? Not to mention you remove the dependency from the Shared Library).

Ideally, you could have the business objects on which your shared library depend on this extra project too. If the business objects are too complex, you could also transform them into interfaces.

You will have both projects not depending on each other, but only on another project with only "dummy" objects (no logic):

Business ---> Interfaces and value objects <--- Shared Library

Now those are decoupled =)

Related questions

Singleton by Jon Skeet clarification

public sealed class Singleton { Singleton() {} public static Singleton Instance { get { return Nested.instance; } } class Nested { // Explicit static constructor to tell C# compiler // not to mark type as beforefieldinit static Nested() {} internal static readonly Singleton instance = new Singleton(); } } I wish to …

Read More
How do I design a Data Access Layer appropriately?

I have the following Data Access Layer (DAL). I was wondering if it's set up correctly, or if I need to improve it? public class User { } //Persistence methods static class UserDataAccess { UsersDAL udal = // Choose SQL or FileSystem DAL impl. InsertUser(…

Read More
Instantiate an object with a runtime-determined type

I'm in a situation where I'd like to instantiate an object of a type that will be determined at runtime. I also need to perform an explicit cast to that type. Something like this: static void castTest(myEnum val) { //Call …

Read More