Summary
In this chapter we have come to the end of the basic configuration for automated delivery of .NET solutions. We have built successively upon a set of initially simple scripts, and maintained that simplicity as we have increased the number of applications using the process. This has been possible through the implementation of a set of standards that are not too intrusive, but are effective to provide the necessary hooks for build automation as we have defined them.
Specifically in this chapter we have used CruiseControl.NET to provide a harness to encapsulate the build process we have developed, but also to implement continuous integration for our applications.
In subsequent chapters we will focus on the development of more advanced features to the system we have in place to squeeze some more functionality out of NAnt and CCNet while also using some other tools.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Further Reading
There is a good comparison of various CI tools in Open Source.NET Development: Programming with NAnt, NUnit, NDoc, and More by Brian Nantz (Addison-Wesley, 2004).
Rights and permissions
Copyright information
© 2005 Marc Holmes
About this chapter
Cite this chapter
Holmes, M. (2005). Continuous Integration. In: Expert .NET Delivery Using NAnt and CruiseControl.NET. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-0023-9_6
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0023-9_6
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-59059-485-8
Online ISBN: 978-1-4302-0023-9
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)