Several basic tools used to support Continuous Integration were ported to the .NET environment during the 1.0 release of the Framework. Other tools, such as CruiseControl and Clover, have been ported more recently. Furthermore, certain other tools such as NDoc are indigenous to .NET and only conceptually related to their Java counterparts (Java Doc, in this case). For the most part, articles written to date about these tools have addressed only a subset of the tools (usually NAnt and NUnit), thus failing to weave together a holistic Continuous Integration solution. Moreover, the unit-testing examples are function based and fail to address the database-driven reality of today's enterprise applications.

In this two-part article, I introduce a complete Continuous Integration solution that encompasses automated builds, data-driven unit testing, documentation, version control, and code coverage.

Author: Thomas Beck
Published: Dr. Dobb's Journal, August, 2004
(Registration necessary)