concept property INJECTION in category .net

This is an excerpt from Manning's book Dependency Injection in .NET.
Essentially, this is how AUTO-WIRING works, although it’s more complicated than that. DI CONTAINERS also need to take care of LIFETIME MANAGEMENT and perhaps address PROPERTY INJECTION as well as other, more special creational requirements. The salient point is that CONSTRUCTOR INJECTION statically advertises the DEPENDENCY requirements of a class, and DI CONTAINERS use that information to AUTO-WIRE complex object graphs.
In this section, we look into the issue concerning cyclic DEPENDENCIES, including an example. When we’re finished, your first reaction should be to try to redesign your DEPENDENCIES. If that isn’t possible, you can break the cycle by refactoring from CONSTRUCTOR INJECTION to PROPERTY INJECTION. This represents a loosening of a class’s invariants, so it isn’t something you should do lightly.
Table 6.1. Some redesign strategies for breaking DEPENDENCY cycles
Strategy
Description
Events You can often break a cycle by changing one of the ABSTRACTIONS to raise events instead of having to explicitly invoke a DEPENDENCY to inform the DEPENDENCY that something happened. Events are particularly appropriate if one side only invokes void methods on its DEPENDENCY. .NET events are an application of the Observer[7] design pattern, and you may occasionally consider implementing it explicitly. This is particularly true if you decide to use Domain Events[8] to break the cycle. This has the potential to enable true asynchronous one-way messaging. PROPERTY INJECTION If all else fails, we can break the cycle by refactoring one class from CONSTRUCTOR INJECTION to PROPERTY INJECTION. This should be a last-ditch effort because it only treats the symptoms.