Resolving circular dependencies with dependency injection
.net, architecture, circular-dependency, dependency-injection
Solution
If you have circular dependencies between two objects, it means you need a third object, on which the two objects will depend on, so they won't depend on each other. Here is an article that is the exact solution to your problem:
http://misko.hevery.com/2008/08/01/circular-dependency-in-constructors-and-dependency-injection/
Problem
I've seen several articles on various websites that propose resolving circular dependencies between .NET assemblies by using dependency injection. This may resolve the build errors but it's not really resolving the circular dependency, is it? To me, there seems to still be a logical error in the architecture. Am I crazy or do others agree? - This is a less than stellar use of DI? - Not the appropriate way to solve circular dependency issues?