title: using a base controller for entire asp.net MVC 4 project
body: <p>I am thinking of using a base controller for the entire MVC 4 project that I am working on. I have found conflicting views online about it and not really sure if it is against best practices or if it is just a matter of personal preference.</p>
  
  <p>Here is a stackoverflow post that says <a href="https://stackoverflow.com/questions/6119206/what-are-good-candidates-for-base-controller-class-in-asp-net-mvc/6119341#6119341">dont do it</a> </p>
  
  <p><a href="http://odetocode.com/Blogs/scott/archive/2010/06/28/action-filter-versus-controller-base-class.aspx" rel="nofollow noreferrer">Here</a>  is a post that has shown how to do it like there are no harmful effects of it. <a href="http://stevehorn.cc/blog/aspnet-mvc-testing-base-controller.html" rel="nofollow noreferrer">Here</a> and <a href="https://stackoverflow.com/questions/11892294/inheriting-a-base-controller-with-constructor">here</a> as well they explain its usage where no one really is pointing out that it is bad practice or could lead to any issues going forward. </p>
  
  <p>So what really is the view on using a couple of base controllers in an MVC 4 project? Good? Bad? </p>
  
  <p><strong>Edit</strong></p>
  
  <p>I'd also like to point out that my immediate goal for using a base controller is so that I can have the Authorization done in one controller and so that all the controllers dont need to have the Authorize attribute. I will create separate base controllers for each role. Since the roles are never going to change I will never need to create another base controller for another role. What do you think of this way of going about designing the controllers? </p>
  
  <p>Thanks for your time.</p>