title: Why pass a parameters of multiple services to mvc controller?
body: <p>I'm new to asp.net mvc world mostly a windows developer moving to web. Be nice...</p>
  
  <p>I found ridiculous when I look at many examples of asp.net mvc web applications that the pass to their controllers a list of services </p>
  
  <p>Like this </p>
  
  <pre><code>public CustomerController(ICustomerService customerService,
                  IAnotherService anotherService,
                  IYetAnotherService yetAnotherService,
                  IYetAgainAnotherService yetAgainAnotherService,
                  etc...
  </code></pre>
  
  <p>Would not be better to do something like</p>
  
  <pre><code>public CustomerController(IServices services)
  {
  }
  
  public interface IServices 
  {
      ICustomerService  CustomerService{get;set;}
      IAnotherServiceService  AnotherService{get;set;}
      IYetAnotherServiceService  YetAnotherServiceService{get;set;}       
  }
  </code></pre>
  
  <p>Am I missing the obvious?</p>
  
  <p>As anybody implemented the way I suggest in mvc4 or mvc5. I know mvc6 does it.
  But I cannot use mvc6 at work.</p>
  
  <p>Any samples using DI?</p>
  
  <p>Thanks </p>