NET Core: Are MVC Controllers default Singleton?

Question

I would like to know if the Controller classes of .NET MVC Core are default Singleton?

If not, then do the Framework creates multiple objects of Controller class for each and every request? Isn't it an overhead and costlier to create a new instance of such classes?

In other programming languages like Java, there is only one Instance of Controller class created (Servlet) and each and every request is handled with a new Thread. Doesn't it similar in .Net?

`do the Framework creates multiple objects of Controller class for each and every request?` - yes. — GSerg, Aug 19 '19 at 08:58
Possible duplicate of [ASP.NET MVC: Is Controller created for every request?](https://stackoverflow.com/questions/5425920/asp-net-mvc-is-controller-created-for-every-request) — GSerg, Aug 19 '19 at 09:00

score 5 · Answer 1 · answered Aug 19 '19 at 09:02

They're actually declared as Transient:

public static IMvcBuilder AddControllersAsServices(this IMvcBuilder builder)
{
    if (builder == null)
    {
        throw new ArgumentNullException(nameof(builder));
    }

    var feature = new ControllerFeature();
    builder.PartManager.PopulateFeature(feature);

    foreach (var controller in feature.Controllers.Select(c => c.AsType()))
    {
        builder.Services.TryAddTransient(controller, controller);
    }

    builder.Services.Replace(ServiceDescriptor.Transient<IControllerActivator, ServiceBasedControllerActivator>());

    return builder;
}

Taken from: https://github.com/aspnet/AspNetCore/blob/c7cb8467bfce721e2d66ef3862cd8c7c1fdbb421/src/Mvc/Mvc.Core/src/DependencyInjection/MvcCoreMvcBuilderExtensions.cs

Line (150)

NET Core: Are MVC Controllers default Singleton?

1 Answers1