I presented today at the VSTSUG in Canberra today the new version of TFS Integrator.   At the time I said that I would blog about it so here it is.    So what is in the version of TFS Integrator.   Well firstly there has been two major changes:

  1. ContinuousIntegraton.xml and DependencyReplication.xml are now stored inside TFS. 
  2. New Setup has been developed that installs the service and updates the TFSIntegrator.exe.config file with the configuration settings.

Besides this two major enhancements, there have been fixes to perform case insensitive checks on all paths.  There have been some instances where the case of a directory has cause TFSIntegrator not to start a build or perform a dependency replication, this errors should have been fixed with this release.

So lets tackle the first new feature.    After some discussion and real life administration of TFS on large projects it quickly became apparent that storing the configuration files in c:\program files\TFSIntegrator doesn’t work, especially for the dependency replication file.   As a result, I decided to store them inside TFS.  This has a number of benefits:

  1. The files are now versioned, so changes to them over time can be tracked. 
  2. Instead of having one set of config files for your whole TFS installation the config file are now maintained on a Team Project level.

In terms of the second new feature we wanted to make the installation process a little smoother.  So now the installation processs is only a couple of steps rather than runing a setup project, then running the TFSIntegrator.exe to install the application and configuring a service.  

So the new version of TFS Integrator can be found here.

The obvious question after this is where to from here.  The top three items on the list are:

  1. Simplification of the DependencyReplication.xml configuration file, because of the new changes.
  2. Getting ready for TFS Orcas.  As a result, TFS Integrator will no longer support Continuous Integration as it will be supported out of the box.    Also, dependency replication will need to be updated to cater for the new changes to the build
  3. A UI to manage the configuration files a little better. It sucks at the moment having to manually edit those configuration files.
  4. The ability to do wild card selections as part of the dependency replication, rather than having to specify individual files.

Shortly I will be posting up installation instructions to install the product from scratch, and to perform an upgrade.