Rationale behind Dependency Injection Container libraries

[Jeff_Mott]

@Lemon_Juice

Such a controller would rather be saying “I don’t need the database connection” when constructing. One method would be saying “I need the database connection to run”.

If you’re dependency injecting your controllers, which you seem to be, then you should only have one action per controller.

See this other discussion for more details:

Application layer design: Is it more beneficial to have one action per class?

First, a quick disclaimer for all involved in this thread: My response assumes we’re talking about the traditional, web MVC. With that out of the way, I think one vs many actions per class depends on whether you want your controllers to use a service locator or be a dependency injected service. If you want your controllers to be a dependency injected service, then one action per class is the way to go. If you had multiple actions, then the controller’s constructor would have to accept depende…