c# - Can I make an ASP.NET Core controller internal?

Question

ASP.NET (and Core) controllers need to be public.

Problem is I have a controller which depends (in its constructor) on something internal. And that dependency depends on something internal, which depends on something internal, etc. So I need to make the controller internal as well.

But then it won't be discovered by the controller factory.

Is there a way to make an internal controller discoverable?

Answer 1

If you want to include internal controllers, you can provide your own implementation of the ControllerFeatureProvider class which is responsible for determining whether a type is a controller or not. In the following example I have created an implementation that looks for controllers implementing a custom base class and falling back to the default implementation for all other cases. In this case, the custom controllers will be discoverable despite being internal, while all other controllers will not.

class CustomControllerFeatureProvider : ControllerFeatureProvider
{
    protected override bool IsController(TypeInfo typeInfo)
    {
        var isCustomController = !typeInfo.IsAbstract && typeof(MyCustomControllerBase).IsAssignableFrom(typeInfo);
        return isCustomController || base.IsController(typeInfo);
    }
}

and to register it:

services.AddMvc().ConfigureApplicationPartManager(manager =>
{
    manager.FeatureProviders.Add(new CustomControllerFeatureProvider());
});

You should probably take a look at the implementation of IsController to see how ASP.NET handles edge cases around the types.