9. February 2010 00:43
[UPDATE 6 april 2011]: There is now a post that tells you how you can modify the build process template to use a relative reference path: Customize Team Build 2010 – Part 16- Specify the relative reference path
When you created a new build definition in TFS 2008, there were a few lines in the TFSBuild.proj file that gave you the ability to give hints where your references were stored. This was very useful when you included the external references in Version Control, so you did not need to install the assemblies in the GAC of every development machine and the build server.
In TFS 2010, the build is now based on Windows Workflow, and there is no default option to add the hintpaths (or additionalreferencepaths) where the build can find your external files. You now have to specify the paths as MSBuild Arguments. You can do that as following:
- Find your build definition in the Team Explorer
- Right click on the build and choose “Edit Build Definition”
- In the list on the left, select the “Process” step
- Open the Advanced secion
- Select the MSBuild Arguments property and type the following: /p:ReferencePath=”<mypath>\<myfile>”
You can specify multilple reference paths by adding multiple paths splitted by ';', like /p:ReferencePath="c:\builds\...\path1;c:\builds\...\path2".
I have not found a resolution yet to make this path relative.