Headspring
agile. software. consulting.

The Tarantino Project

Our moms taught us to share.

Because so much of our efficiency comes from open-source sharing and re-use of successful code modules, we believe in the power of open source. So much so that we frequently share our own code with other developers; yes, even our competitors.

The Tarantino Project

Our Preferred Toolkit

Tarantino.zip contains many useful .dll files (NHibernate, RhinoMocks, StructureMap) and programs (NAnt, Subversion) which comprise a common set of tools which Headspring uses for Greenfield applications. Additionally, the Tarantino project contains a database change management system.

A common Headspring .NET application is structured as such:

  • Typically, we keep source code in Subversion repositories. NAnt scripts build from the repositories to staging and production servers. In doing so they also update a database at each build locale with any pertinent SQL scripts not yet run against the database. (A progressive history of SQL scripts is kept for each project.)
  • Our applications themselves break up the projects within a given solution into the Onion Architecture. The User Interface (front end) references both the Domain (business logic) and the Infrastructure (database integration). The Infrastructure references the Domain (instead of the other way around in traditional layered architecture) leaving the Domain as the autonomous, independent center of the application. Domain objects are loosely-coupled to counterpart data managers in the Infrastructure by way of StructureMap.
  • Separate Unit Test and Integration Test projects exist for both the Domain and the Infrastructure. Objects are often mocked in tests using RhinoMocks.
  • NHibernate is used for database integration.

A glimpse at Tarantino database management:

Download Tarantino

 

© 2001-2010 Headspring. All rights reserved.
Proudly headquartered in Austin, Texas