Castle.Windsor.Extensions.DependencyInjection: Transient services are not disposed.

• Have a controller dependent on a transient service.

Component.For<ITransientService>().ImplementedBy<TransientService>().LifestyleTransient(),

or with MSInjection

services.AddTransient<ITransientService, TransientService>();

• When using MS injection the service is disposed right after the controller is disposed.
• When using Windsor the service is disposed after application shutdown.

Project to test out this scenario: https://github.com/AntonioDrusin/WindsorNetCore31Tester

It is inconsistent that the behavior of transient services is different between using MSInjection and CastleWindsor. The behavior is also inconsistent with how Transient services work in Windsor.

The planned use for this extension is to be able to use our current windsor registrations in Net Core 3.0. With this difference in behavior (transient services not being freeed until shutdown) that won’t be possible.

[AntonioDrusin]

The solution was very simple. We had to give windsor control over the creation of the controller. https://andrewlock.net/controller-activation-and-dependency-injection-in-asp-net-core-mvc/#the-servicebasedcontrolleractivator

Simply calling:

            services
                .AddControllers()
                .AddControllersAsServices();

fixed my issue.

I think the only thing needed for this issue to go away is to document this extension. I think that the LifestyleNetTransient still has value if you do not want to use windsor to resolve the controller.

[nativenolde]

I do not understand very well the concept of different semantics of transient. When I register a transient service in castle windsor (outside of the Microsoft DI framework), I always observed the service being released as soon as the class dependent on it was released. if A depends on B and A is released, then B is released as well.

That’s also my understanding of a transient lifestyle and probably that of most developers out there.

If windsor should be used as implementation of microsoft extensions dependency injection, it has to adopt the imposed principles, at least in my opinion. To have a separate “net-transient” lifestyle could be confusing and should be avoided.