Finally, I had enough with my weekly backup to DVD-R discs. 3 x 4.5Gb DVD-Rs every Monday. Even with the burning spread across three PCs (server, workstation and a laptop) it was a good 90 minutes for burning and verification to complete. There was the occasional duff burn in there too, and while it's burning you can't modify the files you are backing up either. Grrrr. I didn't want to automate the backups overnight. As I am environmentally minded, when I'm not in the office I don't like my PCs being...

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/T8S

Here's the culmination of my research into CI Factory and how I'm not using it to develop my open source RapidDB libraries. This is a fairly personal setup, as it only has a single developer (me), two development machines (currently an office desktop PC and a roaming laptop) and a build server which is not publicly accessible via the Internet. An MSDN and Microsoft Partner Action Pack subscription are busy covering my software license requirements. Summary: Development PC 1 : Desktop, XP Pro SP2,...

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/T7E

CORRECTION - now one week earlier, on 17th May (was 24th May previously). A quick plug for the London .NET user group geek dinner on 17th May. Zi has setup a page on the .NET user group wiki here so sign up and vote for your favourite eatery. See you there. Technorati tags: geek dinner, community, london .Net User Group...

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/T4Z

I decided to add some unit tests into my first CI Factory project. First I used a reference to MbUnit.Framework.dll in my test project, this is the unit test framework which ships with CI Factory, and all worked fine. No disrespect to MbUnit, but I decided I really wanted to use NUnit so I can utilise the larger amount of documentation and community knowledge that exists for NUnit (even though it might not be as flexible as MbUnit). So I added NUnit 2.2.8 (.NET 2.0 version) underneath my CI Factory...

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/T3V

A minor glitch while getting CI Factory up and running. I discovered how important it is to make sure that you keep your version of SVN.EXE (command line SubVersion) in step with that of TortoiseSVN. As TortoiseSVN informs you of upgrades, I'd happily updated it to v1.4.x automatically, leaving my SVN.EXE at 1.3.x. The gotcha was that the installation of CI Factory was fine - it used the older v1.3.x client to create the project tree. After I had used TortoiseSVN to add some projects, it was only...

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/SxB

Before we dive in make sure you read my introduction post here, and that you have followed the screen cast on how to setup CI Factory. My notes will basically follow that procedure and highlight the differences when you have development tools on your D: drive. This is an early list, but hopefully it should give people pointers on how to get going quickly; I'm assuming that your development PC already has Visual Studio 2005, and SubVersion 1.4.3. In addition I had to install NCover 1.5.5 beta and...

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/SnN

A friend from the London .NET users group, Peter Ibbotson, on hearing that I had started looking into Cruise Control .NET for continuous integration said that before doing anything I should look at Zi Makki's blog about CIFactory, a master setup tool for creating a source code tree complete with various tools such as SubVersion, NCover, NDepends all hooked into CruiseControl.NET with NAnt as the build script automating the processing. Well, I've just spent a challenging but very satisfying day and...

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/SnL