SP2010 Continuous Integration – pt 6: Integrating SPDisposeCheck and other tools into the build

Tools such as SPDisposeCheck are great for developers, but having to remember to run them isn’t! This is yet another reason why having an automated build is a good idea – you get to offload the responsibility for running such tools to the computer, and we all know computers do not forget. It seems a while now since I wrote this article, but the MSDN SharePoint Developer blog finally has my step-by-step guide on adding tools into a TFS automated build. The process I describe works for SPDisposeCheck, but also any other tool that can be called from the command-line.

See Integrating Additional Tools in a SharePoint Continuous Integration Build

Here’s an idea of what your team would see in the build report each morning (after an overnight build has run):

This concludes the article series on Continuous Integration for SharePoint projects. The full list is:

1. Benefits of Continuous Integration
2. TFS 2010 Build installation/config (Kirk Evans)
3. Creating your first TFS build process for SharePoint projects
4. Implementing assembly versioning
5. Using PowerShell to deploy WSPs from build output
6. Running coded UI tests as part of a build
7. Integrating Additional Tools in a SharePoint Continuous Integration Build