Community TFS FAQ

This article is in a draft stage.

Setting up an account

  • This applies to only community team members as Church workforce can use their Active Directory account and do not need a separate TFS account. We are working on options in the future that will remove this synchronization step for community members.
  • Go to This application will prompt you for your LDS Account username and password, validate these credentials, and then create a TFS Account with the same username and password. If you change your LDS Account password, you will need to come back to the application and enter your new credentials which will be synchronized with your TFS account.

Giving a contributor permissions to the TFS project

  • TFS relies on Windows security too for core pieces of its security model because community contributors are not part of the Church's Active Directory domain the standard TFS GUI permission tools can be used to define security groups and view the users that are in those groups, but not to grant access. This is because from the client machine the user account being granted access cannot be resolved. Instead, a standard command-line utility (TFSSecurity.exe) that comes with the TFS tools installation is used.
  • Open up a Visual Studio Command prompt.
  • Type in the following command line call substituting the appropriate parameter values (in bold below):
  • For the domain parameter, it should be noted that the domain for Church workforce contributors will be LDS and for community contributors will be W1738.

Accessing TFS from the Web, Visual Studio, or Microsoft Test Manager

  • TFS on the web is available from
  • TFS for Visual Studio or Microsoft Test Manager (MTM) can be accessed by specifying as the server URL. With MTM, if you haven't previously configured the server in Visual Studio you will need to type in so MTM knows to use HTTPS instead of the default HTTP.

Setting up a build definition

  • Setting up a build definition using the ICS Community TFS should operate like setting up a build definition on any TFS Server.
  • The drop location should point to \\\drop\<project>\.
  • Builds are encouraged to use the StackBuildProcessTemplate.xaml which is found in the Community TFS Source Control at the path $/MSStack/TFS/BuildProcessTemplates. This custom template handles stamping the assemblies with a common assembly version and provides a simple configuration parameter to enable the creation of MSDeploy packages. See the appendix for more details on creating a build definition using the StackBuildProcessTemplate.

Retrieving Builds

Builds will be available externally at From there you can pull down the bits based on your permissions. To get permissions to a drop location contact the project administrator for access.

Granting access to drop locations

You must have access to grant permissions to the drop location. Currently, only Church employees can grant access to drop folders (we are working on changing this in the future). To grant access use the following command-line.

Note: If no one on the project including the administrator has access, send a request to and the TFS administrators will set up the initial access for your team.

CACLS <directory> /G <user>:C}}
   /G user:perm  Grant specified user access rights.
           Perm can be: R  Read
                        W  Write
                        C  Change (write)


Details about Assembly Versioning and using the custom LDS .NET Stack Build Process Template can be found in the Builds and Version Control article under:

This page was last modified on 7 December 2012, at 15:17.

Note: Content found in this wiki may not always reflect official Church information. See Terms of Use.