Running MSDeploy to a remote box from inside a TFS 2010 Build (Part 2)
Another follow up post, this time to the one on MSDeploy. As I said in that post a better way to trigger the MSDeploy PowerShell script would be as part of the build workflow, as opposed to a post build action in the MSBuild phase. Doing it this way means if the build failed testing, after MSBuild complete, you can still choose not to run MSDeploy. I have implemented this using an InvokeProcess call in my build workflow, which I have placed just before Gated checking logic at the end of the process template. ...