Implementing resource oriented controllers in ASP.NET MVC
Posted by: Pablo M. Cibraro (aka Cibrax),
on 25 Jan 2012 |
View original | Bookmarked: 0 time(s)
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...