TeamCity is also a Java-based CI server package.  The TeamCity installation and configuration is quick and easy.  The fact that it is Java-based should not be an impediment to .NET development shops.  The TeamCity server is a primary component, but the browser-hosted interface serves as the primary way to administer TeamCity users, agents, projects, and build configurations.

The TeamCity browser-hosted dashboard is superb.  It provides project status and reporting information suitable for a broad range of users and project stakeholders.  It provides build progress, drill down detail, and history information on the projects and configurations.

With TeamCity, there is a system tray utility to provide feedback on build status and progress.  The tray utility is useful so build notifications are received in the tray instead of by email.  The TeamCity tray application notifies on events such as whether the most recent build was successful or failed.

There are a lot of good reasons to choose TeamCity.  The product is very well documented and there are a lot of examples and tutorials available.  Out on the Internet, there are many postings ranging from setting up basic CI with TeamCity to advanced topics such as using TeamCity’s built-in NUnit test runner.

Some other reasons to choose TeamCity include:

Note that you can run as many instances of Professional Edition Server as needed.  Larger organizations may require the purchase of the Enterprise Server version.