Jonathon Rossi

Compiling for .NET 2.0 with Csc 3.5 under NAnt

Jonathon Rossi — Mon, 06 Jul 2009 12:52:35 GMT

The Castle Project dropped support for .NET 2.0 on the trunk last year, however as project leader of DynamicProxy I decided we would continue to support DynamicProxy on .NET 2.0 until downstream projects (e.g. NHibernate) no longer support it.

Castle Core has had a reference to System.Core for quite some time, however it is conditionally compiled with support for .NET 2.0, Silverlight and Mono.

Up until recently we had been making sure we didn't use any C# 3.0 features in DynamicProxy so we could still build for .NET 2.0 with the .NET 2.0 compiler, however this has always been a little annoying.

I worked out that changing the frameworkdirectory attribute on the net-2.0 framework element in NAnt.exe.config will make NAnt use Csc 3.5. You just need to change 'v2.0.50727' to 'v3.5'.

With this change we can now use the var keyword, lambda expressions, object initializers and anonymous types.

Castle NCover and NDepend NAnt targets

Jonathon Rossi — Mon, 08 Jun 2009 11:01:44 GMT

I forgot to mention the new targets in the previous posts. If you want to generate either the NCover or NDepend reports like the ones available from TeamCity use these targets.

If you run "nant coverage" it will enable running nunit-console under NCover to produce the coverage XML log files, and run a build. The target will also generate the summary coverage report.

Using "nant ndepend" will run a build and generate the report from the artifacts.

NDepend for the Castle Project

Jonathon Rossi — Sun, 07 Jun 2009 16:13:11 GMT

I'd like to start by thanking Patrick Smacchia from NDepend for the free open source licence of NDepend Professional for use at the Castle Project.

I have finally got around to changing the build scripts to have NDepend running in our build so we can generate the NDepend code analysis report.

You can view the report in the artifacts of one of the coverage/NDepend builds, or with this direct link to the last successful build.

As you can see for yourself the report contains heaps of valuable information. I am yet to get a chance to blog about several things I have realised while playing with NDepend, which I plan to do in the next few weeks when I get some more time.

For now, you can take a look at the report for yourself.

Code Coverage for the Castle Project

Jonathon Rossi — Sun, 07 Jun 2009 14:44:02 GMT

I'd like to start by thanking the guys from NCover for the free open source licence of NCover Complete for use at the Castle Project.

I have finally got around to changing the build scripts to have NCover running in our build so we can generate code coverage reports.

You can view the summary report in the artifacts of one of the coverage builds, or with this direct link to the symbol module report for the last successful build.

As you can see for yourself Castle's sequence point code coverage is currently at 61.2%. As for individual projects here are just a few:

ActiveRecord: 65.6%
Core: 31.7%
DynamicProxy: 86.4%
MicroKernel: 67.3%
MonoRail Framework: 49.6%
Windsor: 79.5%

Interestingly, Castle Core has the lowest code coverage of any project coming in at 31.7%, while it is at the base of all Castle projects, however it is very stable and solid.

As expected, NVelocity has the highest maximum cyclomatic complexity by far because of several very long and complex methods.

I am yet to set up the build to generate the full HTML coverage report which displays the source code with annotated coverage information.

TeamCity Duplicates Finder Source Code Permissions

Jonathon Rossi — Fri, 15 May 2009 22:18:07 GMT

I set up the .NET Duplicates Finder feature of TeamCity yesterday for Castle, and was later told that a guest (set up as the project viewer role) could not see the source code in the report. TeamCity was displaying "You do not have enough permissions to view this file content" instead of the source code.

I remembered today that the roles in TeamCity were made configurable in 4.5 and adding the 'View VCS file content' permission to the project viewer role now allows everyone to see the source code in the report.

This report provides some interesting results and is well worth setting up. One caveat is the requirement of a Visual Studio solution file which TeamCity uses to search for the source code.