Guy Mahieu’s Blog

I guess people put todo’s in their code for different reasons, it can be lazyness (I’ll write this hard/boring piece of code later), unclear requirements or maybe a debate is needed before a certain choice can be made.

Be that as it may, some todo’s need to be solved more urgently than others: “TODO: implement database logic” could be more urgent than “TODO: remove obsolete method”, but removing an obsolete method will probably be easier to do, so it might make sense to do it right away.

Visual Studio 2003 gave you a nice list of all the todo’s in your solution, but for some reason Visual Studio 2005 only does this for currently opened files. In the project I am current working on, we wanted a clear report of all todo’s in our code to make sure that they are solved as soon as possible. Since we already have a CruiseControl.NET server running, we decided to have our continuous integration build generate the TODO report for us. The samples in this post are valid for CruiseControl 1.1.

Continue Reading »

JetBrains, the people that gave us IntelliJ IDEA and Resharper, have released the public beta of their new Integrated Team Environment called TeamCity.

Some of the features:

• Rich web interface
• Continuous Integration support
• Code coverage
• Build grid
• Static code analysis
• Support for both java and .net
• Building: support for ant, maven, NAnt and MSBuild - IntelliJ projects and Visual Studio solutions can be built directly without build scripts
• Testing: jUnit and NUNit support
• VCS integration for: Perforce, CVS, Subversion and Visual SourceSafe
• and my personal favorite: Delayed Commit - changes are committed to the VCS only if all tests are passed

Give it a test drive at http://teamserver.jetbrains.com/