tf.exe on tfspreview

Question

I need to get the ChangeSetId in tfspreview for our continuous integration. I just need this single number nothing else. I tried all possible MSBuild tasks that I could find, but there is always another smaller issue stopping me.

For MSBuild.ExtensionPack.Tfs.TeamBuild I get :

Could not load file or assembly 'Microsoft.TeamFoundation.Client, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

and for TfsClient -task in community-pack (which is generating following exec: tf.exe history . /StopAfter:1 /noprompt /format:detailed /recursive) I get:

The specified task executable could not be run. The system cannot find the file specified

My question is; Is it possible to execute TF.exe on tfspreview server? or can I get the assembly Microsoft.TeamFoundation.Client on the build server to execute one of these two tasks?

Are you running from a x86 or x64 console? The TFS packages are x86 only and don't work in x64 or AnyCPU configurations. — Ray Hayes, Aug 07 '12 at 10:15
its running in tfspreview, which is microsoft cloud service, and they are usually x64 OS but if the tfs client is x86 than it will be x86, but the used packages are the one developed by microsoft so it can not be compatibility issue — zebra, Aug 09 '12 at 02:22

score 7 · Answer 1 · answered Oct 16 '12 at 21:19

Alright, I am here to tell you that this IS possible without writing your own custom task, using the API, etc... there are a number of articles out here on StackOverflow but the ones with solutions do not appear to work for TFS 2010. I just spent an entire day banging my head against the wall :D

You need to install the MSBuild Community Tasks. Make sure you get the latest version from here: https://github.com/loresoft/msbuildtasks. The latest appears to have been updated and rebuilt against the TFS 2010 assemblies.
You are going to use the MSBuild.Community.Tasks.Tfs.TfsClient task. The reason you are getting that error about not being able to run the executable is because this is an MSBuild ToolTask and you need to pass in the path to the executable as a property (ToolPath) to the task.
The TfsClient task is just a wrapper to tf.exe and the task is missing a lot of possible features for handling the switches in an MSbuild-y way. (and the documentation for this task is nonexistant - i had to look at the code) Luckily I figured out that you can enter all of the command line switches as part of the command itself.

So your final call will look something like this...

<MSBuild.Community.Tasks.Tfs.TfsClient ToolPath="$(PathToTfTool)"
                                   Command="history /collection:$(TfsProjectCollectionUrl) /stopafter:1 /version:T /format:detailed $(VersionControlPathForBuildWorkspace)"
                                   Recursive="true"
                                   >

<Message Text="TFS ChangeSetNumber: $(ChangesetNumber)" />

And after 22 miserable failed builds or builds with no data I finally got... TFS ChangeSetNumber: 41

YAHOO!

Got the command from Martin Woodward: http://www.woodwardweb.com/vsts/determining_the.html MAKE SURE YOU USE THE /DETAILED SWITCH OR IT WONT RETURN THE CHANGESET. I had to look at the code for the task and figure out how it was parsing the output from tf.exe to figure this out.

Code for TfsClient is here for reference: https://github.com/loresoft/msbuildtasks/blob/master/Source/MSBuild.Community.Tasks/Tfs/TfsClient.cs

Okay, I fooled around with this too! Your post is extremely helpful, but I had to add in order to get mine to work. Thanks!! — Ci3, Dec 06 '13 at 20:16

score 2 · Answer 2 · edited Feb 02 '14 at 18:55

Here's the line of code that worked for me.. after several hours and couple of tries. the difference is that I created an output TaskParameter element within the

Where:

ToolPath ="C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE" - depends if you're on 32 or 64 bit.

$/WorkspacePath name of the path on my workspace, you can view this using tf workspace command

<MSBuild.Community.Tasks.Tfs.TfsClient ToolPath="C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE"
                               Command="history /s:http://tfsserver01:8080/tfs/collectionname /stopafter:1 /version:T /format:detailed $/WorkspacePath"
                               Recursive="true" >
  <Output TaskParameter="Changeset" PropertyName="ChangesetNumber"/>
</MSBuild.Community.Tasks.Tfs.TfsClient>
<Message Text="TFS ChangeSetNumber: $(ChangesetNumber)" />

But thanks to this thread

score 0 · Answer 3 · answered Aug 13 '12 at 14:06

What exactly does the MSBUILD workflow look like? Are you passing this parameter into MSBUILD or is some custom component grabbing this information while MSBUILD is running?

I've come across the class InformationNodeConverters, which has the method GetAssociatedChangesets that takes in an IBuildDetail and returns a List of IChangesetSummary. This would also require that your changesets already be associated before you get to the MSBUILD task. I'll need to check against my TFSPreview instance tonight to see if I can edit the build template, but I would suspect that you should be able to use something like this.

tf.exe on tfspreview

3 Answers3

Linked