Run a script in your build process
The Team Foundation Build (TFBuild) default template provides the core capabilities that most teams need to build and test their app. Even so, most software projects are unique enough to require teams to add their own business logic. Developing and maintaining a custom build process can be complicated and expensive. But you don’t have to do that if you just want to run a PowerShell script or a batch (.bat) file before or after the system compiles or tests your code.
For example, before you compile, you want to set the version of your assembly files. Or after you compile, you want to control the build outputs that get dropped to your staging location.
You can use the default template to run PowerShell and batch (.bat) scripts before and after you compile your code, and before and after your run your tests.
Before your build process can run your script, you must first upload it:
After you upload your script, reference it from the appropriate place in the build process parameters. If necessary, you can also supply arguments to the scripts.
Pre-build example: Version your assemblies
Even though there are many tasks you might want to perform before MSBuild compiles your code, one of the most common of these might be to apply a version to your assemblies.
Post-build example: Prepare your binaries to be staged
When you set Output location to AsConfigured, TFBuild yields control of which binaries are dropped to you. In this case, TFBuild compiles the binaries and leaves them in the source directory, organized essentially the same way as if you used Visual Studio to compile them locally on your dev machine. The following script gathers some of the typical binary types from the typical locations and copies them to the folder from which TFBuild copies and drops to your staging location.