Implementing resource oriented controllers in ASP.NET MVC - Pablo M. Cibraro (aka Cibrax) - 2 views
-
Jacques Bosch on 27 Jan 12"One common problem with the naming convention and default routing mechanism in ASP.NET MVC is that we tend to group actions in a controller for sharing an URL space. This basically leads to complex controllers with a lot of unrelated methods that break the SOLID principles. Too many responsibilities in a simple class affects maintainability in the long run and causes secondary effects that complicates unit testing. For example, we usually end up with class constructors that receives too many dependencies as it is discussed here in SO."