title: Alternatives to partial controller classes
body: <p>I have moved onto a project that has a <code>public partial class AdminController</code>, there are 15 other classes that implement this partial class. I think this is done so the project can have lots of routes accessible via the <code>"/admin/{methodname}"</code> path.</p>
  
  <p>The primary partial class handles the constructor for all 15 classes and therefore has 13 constructor dependencies.</p>
  
  <p>I don't think this is very pretty but am unsure how to tidy this up so each class can have the dependencies it needs but keep all routes going to <code>"/admin/{methodname}"</code></p>