5

I have part of a code that has dependencies that look as follows:

public class MyPage : Page //ASPX WebForms page
{
    public IPersonBl PersonBl { get; set; }

}

public class PersonBl : IPersonBl
{

    public PersonBl(ISomeMagicBl magicBl){...}

}

public class SomeMagicBl : ISomeMagicBl
{
    public IPersonBl PersonBl { get; set; }

    public SomeMagicBl(/*Other dependencies*/) {...}
}

My module configuration looks as follows

...
builder.RegisterAssemblyTypes(ThisAssembly).Where(t => t.Name.EndsWith("BL")).AsImplementedInterfaces().PropertiesAutowired(PropertyWiringFlags.AllowCircularDependencies).InstancePerLifetimeScope();
...

As can be seen, I have circular dependencies in my classes which I was able to resolve by using the ..PropertiesAutowired(PropertyWiringFlags.AllowCircularDependencies)...

My Question: What exactly does this flag do behind the scenes to solve these circular dependencies??

Juri
  • 32,424
  • 20
  • 102
  • 136

2 Answers2

3

The flag changes the point at which property injection is done for the type from construction time to after the rest of the graph has been created. It relies on one or more of the components in the cycle having some kind of sharing (singleton or per-request) - even with the flag, if all of the components are instance-per-dependency then a kind of cycle will still exist.

Without the flag, Autofac considers all of the dependencies of the component, properties or not, to be prerequisites to letting any other component get a reference to it. As a default this is more reliable.

Nicholas Blumhardt
  • 30,271
  • 4
  • 90
  • 101
  • Perfect, thx. I assumed you applied such kind of strategy, just wanted to be sure :) – Juri Nov 16 '11 at 15:42
1

just for reference, another good way to resolve a circular dependency is by taking a dependency on Func<T>, as long as you don't access the func in the constructor.

flq
  • 22,247
  • 8
  • 55
  • 77