Castle Windsor处理订单

Question

I have a problem with dispose order of resolved components using Windsor Castle. The issue can be demonstrated on the following code

class Program
{
    static void Main(string[] args)
    {
        using (WindsorContainer container = new WindsorContainer())
        {
            container.Register(Component.For<C1>().LifestyleSingleton());
            container.Register(Component.For<C2>().LifestyleTransient());
            C1 c1 = container.Resolve<C1>();
            container.Release(c1);
            Console.WriteLine("Release done");
        }
        Console.WriteLine("Container dispose done");
    }
}

public class C1 : IDisposable
{
    private C2 m_c2;

    public C1(C2 c2)
    {
        m_c2 = c2;
    }

    public void Dispose()
    {
        Console.WriteLine("Dispose C1");
    }
}

public class C2 : IDisposable
{
    public void Dispose()
    {
        Console.WriteLine("Dispose C2");
    }
}

It prints out following:

Release done
Dispose C2
Dispose C1
Dispose C2
Container dispose done

I would expect following output:

Release done
Dispose C1
Dispose C2
Container dispose done

Disposing C2 before C1 can cause serious problem in C1. C1 can still be alive and be processing something. Note that problem disappears when both components are registered with LifestyleSingleton or LifestyleTransient but there still exist cases where registering C2 as LifestyleTransient can be useful.

Is there a way to register or resolve components to solve this problem?

Answer 1

I solved this issue by using a scope and register C1 as Scoped. In this case, the dispose order is correct. But I'm not sure if this is the recommended way.