title: .NET MVC Controller with multiple Repositories and Services?
body: <p>Look at my Controller (I'm using Dependency Injection to manager dependencies):</p>
  
  <pre><code>public RoleController(IRoleRepository roleRepository, ISiteRepository siteRepository, IUserRepository userRepository, IDbContext dbContext)
  {
      _roleRepository = roleRepository;
      _siteRepository = siteRepository;
      _userRepository = userRepository;
      _dbContext = dbContext;
  }
  </code></pre>
  
  <p>Having a class with many dependencies is a code smell? Right?</p>
  
  <p>But, In my example I need to associate <code>Users</code> and <code>Sites</code> in a <code>Role</code>, then I need to these dependencies to doing this association.</p>
  
  <p>Some people on a mailing list I was told that having too many dependencies is a sign that something is probably wrong. But I see no other way. I separated my responsibilities, there is something in that situation I do not know how to treat? Is something wrong?</p>
  
  <p><strong>Update:</strong></p>
  
  <p>I need Repositories and DbContext because DbContext is my UnitOfWork, repositories don't save.</p>
  
  <p>This example is a simple CRUD with some other functionalities like Associations in the View with a GRID.</p>
  
  <p><strong>Update 2:</strong></p>
  
  <p>I'm using a architecture where my UI Layer is the MVC.</p>