title: Keeping a controller thin (too many action methods)
body: <p>I'm working on my first real ASP.NET MVC project and I've noticed that the controller I've been working in is getting rather large.  This seemingly goes against the best practice of keeping your controllers thin.</p>
  
  <p>I've done a good job keeping the business logic out of the controllers.  I use a separate layer for that.  Each action primarily calls a method in the business layer and coordinates the end result based on whether or not the modelstate is valid.</p>
  
  <p>That said, the controller has a large number of action methods.  Intuitively, I would like to break the controller down into sub-controllers but I don't see an easy way to do that.  I could simply break the controller down into separate controllers but the I loose the hierarchy and it feels a bit dirty.</p>
  
  <p>Is it necessary to refactor a controller with a large number of thin actions?  If so, what is the best way to do this?</p>