I recently ran into a TFS user who was trying to create a new build definition for his project. When he check the Process part of the build, no Build process template shows up in the drop down list, And if he tries to download a template, he gets error that the template already exist for that project.
After investigating a while, I came across the TFS group which he was a member of. This group had below two permission “Deny” for Build.
“Deny” permission supersedes all other permission set for any role or permission. You can find this by going to “Build” section of your project and selecting “Security” from the “Action” drop down. And then set “Allow” for above two permission.
This resolved the issue user was facing and able to see and add Build process template to new build.
Have you ever faced an issue where you need to modify or edit a build definition which was create using VS 2010 for TFS 2010 or before? When you try to edit the “Configurations to Build” section of your build definition, you might see some error such as below.
Before you can work with TFS 2010 build workflows you must add a few assembly redirects to Visual Studio 2012 configuration files to enable it to communicate properly with TFS 2010. This section explains how to do that. You will need local administrative privileges to be able to do this.
Navigate to “C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\”
Open devenv.exe.config file in a text editor and navigate to the “assemblyBinding” section.
Add the following assembly redirects as last elements inside the “assemblyBinding” section.