Releasing resolved object on the constructor

If we Resolve an object in the constructor, castle automatically releases the resolved object when parent object is released.

This test fails since MyDisposableClass is released by windsor.

    public class ConstructorResolveTests: TestBaseWithLocalIocManager
    {
        private readonly WindsorContainer _container;

        public ConstructorResolveTests()
        {
            _container = new WindsorContainer();

            _container.Register(
                Component.For<MyDisposableClass>().LifestyleTransient(),
                Component.For<MyClient>().LifestyleTransient()
                );
        }

        [Fact]
        public void Should_Not_Release_MyDisposableClass()
        {
            var client = _container.Resolve<MyClient>();
            _container.Release(client);

            MyDisposableClass.DisposeCount.ShouldBe(0); //But it is 1
        }

        public class MyClient
        {
            private readonly MyDisposableClass _myDisposableObject;

            public MyClient(IKernel kernel)
            {
                _myDisposableObject = kernel.Resolve<MyDisposableClass>();
            }
        }

        public class MyDisposableClass : IDisposable
        {
            public static int DisposeCount { get; set; }

            public void Dispose()
            {
                DisposeCount++;
            }
        }
    }

This is unexpected by me. Because, Resolving was done in a deeper level and I hardly find the actual reason. While this seems reasonable in some cases, it may not be proper always. Can we change this behaviour?

Thanks.

[IanYates]

“externally managed” is me misremembering the appropriate term 😃

Something like

container.Register( Component.For<ISomething>().UsingFactoryMethod(......, managedExternally: true) );

The … represents various overloads available for UsingFactoryMethod. All involve some kind of Func - one with no parameters, one that takes the kernel, another with the kernel & creationContext and another with even more parameters. Choose the appropriate one and set the managedExternally boolean true so that Windsor won’t track the component for release.

[hikalkan]

Yes we can close. Thanks.