title: ASP.NET MVC IoC usability
body: <p>How often do you use IoC for controllers/DAL in real projects? </p>
  
  <p>IoC allows to abstract application from concrete implementation with additional layer of interfaces that should be implemented. But how often concrete implementation changes? Should we really have to do job twice adding method to interface then the implementation if implementation hardly will ever be changed? I took part in about 10 asp.net projects and DAL (ORM-like and not) was never rewritten completely. </p>
  
  <p>Watching lots of videos I clearly understand that IoC "is cool" and the really nice way to program, but does it really needed? </p>
  
  <p>Added a bit later:
  Yes, IoC allows prepare better testing environment, but we also have nice way to test DAL without IoC. We wrap DAL calls to database into uncommited transactions without risk to make data unstable. </p>