This page last changed on Oct 19, 2004 by mroberts.

The CCNet Project Report Web Application is used for reporting the status of all the builds for a project. To install it:

  1. Unzip the distribution as described in Basic Installation
  2. In IIS, map a virtual directory to the 'web' subfolder of your CCNet folder

Make sure you have enabled 'default.aspx' as a 'Default Document' in your IIS config.

For the project report to work, you need to generate build logs on your CCNet Server. To do this, make sure you have setup your Project to have an Xml Log Publisher.

The Project Report Web Application will not work until you have run a build and generated a build log (either for a successful or failed build, it doesn't matter which)

To configure the webapp, you need to set the 'logDir' value in the 'appSettings' section of the web.config file, to be the absolute path of the Xml Log Publisher log directory. The typical value for this is :

  • c: \ program files \ CruiseControl.NET \ server \ projectName \ artifacts \ buildlogs \

If in doubt of what your project build log should be, run a build on the server and then explore your CruiseControl.NET directory to find where the logs are going.
The default log file locations changed in version 0.7 - make sure you have configured your directory correctly. If you want to use the pre-0.7 default location (i.e. the log sub-directory in the web directory), see the note in the Xml Log Publisher documentation.
The Project Web Application will be deprecated in a not-to-far-away release and the replacement will be much easier to configure!

Reporting Multiple Projects

The Project Report Web Application does not support reporting multiple projects. To do this, you'll need to do one of the following:

  • Copy the project report directory to a different location and setup a separate virtual directory
  • Use the the project reporting features of the Web Dashboard

Advanced CCNet Web Application Features

FxCop Summary

The fxcop summary at the bottom of the web page only shows the fxcop rule violations for the files that were included as part of the current build (ie. the files that have been added or modified since the last build). The rationale is that most projects consist of hundreds, if not thousands, of rule violations (according to Microsoft ) Looking through this list, it is very hard to figure out where to start, let alone which violations are relevant to your changes. So the fxcop summary is designed to give you a view at a glance of some fixes that you might want to start making in an area of the codebase that you will be familiar with.
Document generated by Confluence on Jun 26, 2005 17:22