TFS 2010 – Sequential As Opposed To Parallel Builds

A client was asking me this today so I decided to make a quick note and send a link :)

In TFS 2010 when trying to make Sequential builds (i.e. for one you have several interdependent solutions in your automation strategy) in the DefaultTemplate XAML file you have to change the tag to . It should be noted that this is a lot different than TFS 2008. In TFS 2008, in the TFSBuild.proj file the solutions were just ordered correctly and made use of the BuildSolutionsInParallel property. This also required changing the setting for the MaxProcesses in the tfsbuildservice.exe.config file on the build server to a value greater 1, and also to restarting the build service on the build server. This is a lot more cumbersome than changing the type tag mentioned above.


Exploding TFS Groups For User Investigation

When users are using Team Explorer and viewing the group membership for a particular project (Team Project Settings -> Group Membership) it’s pretty easy because explicit users and groups are listed. However, this becomes a problem when you want to view all the users of that particular group. This is very, very evident when the groups are chained, i.e. Group X contains Group Y, which contains Group z, and so forth. This becomes an issue because viewing the security information for a particular security group becomes very limited.

Fortunately, to get around this limitation you can use the TfsSecurity tool, specifically the TfsSecurity /imx command, to get the direct members of the specified group.

It is important to remember that TfsSecurity.exe comes from Team Explorer, not the Visual Studio shell.