Working with Legacy code #4 : Remove the hard dependencies

Posted by andrewstopford on ASP.net Weblogs See other posts from ASP.net Weblogs or by andrewstopford
Published on Tue, 01 Jun 2010 20:54:00 GMT Indexed on 2010/06/01 21:04 UTC
Read the original article Hit count: 517

During your refactoring cycle you should be seeking out the hard dependencies that the code may have, examples of these can include.

  • File System
  • Database
  • Network (HTTP)
  • Application Server (Crystal)

Classes that service these kind (or code that can be abstracted to a class) of these kind of dependencies should be wrapped in an interface for easier mocking. If you team starts refering to the interface version of these classes the hard dependency will over time work it's self free.

© ASP.net Weblogs or respective owner

Related posts about General Software Developm

Related posts about Legacy Code