CCNET with MSBuild and AssemblyInfoTask
Date Published: 17 January 2007
This afternoon I embarked on a quick (hah!) task to fix a problem with my CC.NETimplementation. I’m using CC.NET running on my Team Foundation Server machine. It checks my TFS source control to see when anything in my project has changed, and if it has, it kicks off a build using an MSBuild
So the root of my problem is that when I do a build, updated versions of my Business and Data assemblies (also projects in the same solution, with project references that are stored in the .sln file) are not getting copied into the /bin folder. I was thinking this might be because the version numbers were hardcoded to 18.104.22.168, so I took a look at the AssemblyInfoTaskMSBuild task and quickly got that working (note that it has Y2K7 issues). However, I eventually ran into the problem of how to update my AssemblyInfo.cs files on the build machine since these are kept in my source control. Right now, it’s failing because they’re read-only, so it’s unable to open them for writing. There are solutions on the web to modify AssemblyInfoTask and have it twiddle the readonly bit. There are also options to try and do a checkout/checkin on the files, but this can lead to an infinite loop with the checked-in files triggering a fresh CC.NET build, which updates the AssemblyInfo.cs files, which triggers a new build…
So, a few hours later, I don’t have a good solution for how to integrate CC.NET and AssemblyInfoTask that I’m happy with. However, I do have a bunch of links that others may find useful, and that I’ll probably want to refer to later.
MSBuild and CC.NET Configuration Article – not really related but came up a few times in my search efforts.
AssemblyInfoTask checking out all projects – the exclude and cloak stuff might be useful to hide AssemblyInfo.cs files from CC.NET
Real World CC.NET Article with Great Detail – This is a great post with a ton of good reference material.
At the end of all this, I’m wondering if the original problem with the files not being copied has to do with how they’re set up in source control, so it may be that this was all a dead-end path. However, at some point it would be cool to be able to use AssemblyInfoTask to update my assembly build numbers correctly on the build server.
Steve is an experienced software architect and trainer, focusing on code quality and Domain-Driven Design with .NET.