-1

Guess the title asks the Q really. I want to see what's going on on a step-by-step basis for the build process that I've inherited.

I've only just started to play with WF and whilst I understand it is possible to debug a workflow I've really no idea how to go about it in this instance.

Jonathan Nixon
  • 4,940
  • 5
  • 39
  • 53
Stuart Hemming
  • 1,553
  • 2
  • 21
  • 44
  • Yes it is an exact duplicate! I posted the original Q here and then posted it there when no one appeared the be able to answer it here. – Stuart Hemming Sep 18 '13 at 10:23

1 Answers1

1

If you want to debug a build workflow you have a couple of options.

If you want to remotely debug, i.e. you want to run the build on a build agent but run VS with your xaml and custom activity code on your desktop then you need to use the remote debugger and attach to the TFSBuildServiceHost.exe process. It can be a bit of a pain as you will need to put the debug version and pdb files of any custom assemblies you've got.

You could also install the TFS build agent on your desktop and attach it to your controller (if you have permissions) you can then debug locally the same way you would any other .net project.

Or run up VS on the build agent itself and debug from there.

I've done all of these, running VS on the build agent is easiest, but I must admin I've only really been able to step though the code in the custom assemblies. I've never managed to get the debugger to his a breakpoint in the XAML itself.

James Reed
  • 13,873
  • 51
  • 60
  • Thanks James. I've only just take over the management of the build system and with next to no handover. Getting to gripds with what's happening is proving, _challanging_! – Stuart Hemming Sep 17 '13 at 16:52