1.

This component uses th

Figure 1
Custom build process template

Note: The Release Management build process templates can be found in the
%ProgramFiles(x86)%\Microsoft Visual Studio 14.0\Release Management\bin folder.

2. As a quick aside, the custom build process template also contains the logic to tokenize your
configuration files. This logic assumes that in your solution, you have two versions of your
configuration files. One version is your normal configuration file used during local development,
and the other is a corresponding file that has the same content, except that instead of having
local values for your variables, tokens have been put there. The build activity will swap those
two files before doing the build, so that you end up with the tokenized version of the
configuration files in the drop location.
3. Here is an example of how to achieve this: Let’s say your solution contains a file called
web.config. You would need to copy that file (and keep them in sync), and name it
web.config.token. Your web.config file will stay the way it is now (and that will be used when
you run the app locally). The web.config.token file will contain tokens instead of values.

Figure 2
Example of token file

4. Back to our build configuration, scroll down to the Release Management section of the build
process parameters and note that the Release Build parameter is set to ‘True’. Both the build
 definition and Release Management need to be configured in order to allow a build to trigger a
release.

Figure 3
Location of Release Build option

Note: In the case of a nightly build, it may make sense to set the Release Target Stage to be
something other than production, perhaps a development or QA stage, but for demonstration
purposes, we will take the release all the way to production.

5. Press Ctrl + S to save the build definition. Everything should now be in place for a continuous
integration scenario where a source check in will trigger both a build and a release.

Task 2: Initiating a Release using Continuous Integration

1. In Team Explorer – Home, double-click on the first FabrikamFiber.CallCenter.sln solution (the
Dev branch).

Figure 4
Loading FabrikamFiber solution
2. Launch Internet Explorer from the taskbar and select the FF DEV button from the favorites bar
to load the Fabrikam Fiber site currently deployed to the development environment. You’ll have

3.