As earlier you need to add reference of following assemblies

1. Microsoft.TeamFoundation.dll
2. Microsoft.TeamFoundation.Client.dll
3. Microsoft.TeamFoundation.Build.Client.dll

which will be available under – C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ReferenceAssemblies\v2.0\ location.

And here is the code snippet

var tfsName = "http://dotnetthoughts:8080/tfs/defaultcollection";
var tfs = new TeamFoundationServer(tfsName, new UICredentialsProvider());
tfs.EnsureAuthenticated();
if (tfs.HasAuthenticated)
{
	var buildServer = tfs.GetService(typeof(IBuildServer)) as IBuildServer;
	var buildDefinition = buildServer.GetBuildDefinition("", "");
	buildServer.QueueBuild(buildDefinition);
}
catch (Exception exception)
{
    MessageBox.Show(exception.Message);
    throw;
}

Here is how it works, we are connecting and getting the TFS Server, then getting the Build Server using GetService method. And to get the build definition instead of the earlier post(to get all the Build definitions, we are passing “*”), we need to specify the Team project and Build name(Build definitions are unique per team project in TFS). Then we can call QueueBuild() method on Build server object, with build definition as the parameter, which will queue the build definition default values.

Happy coding

Cloaking used to prevent users from viewing specified workspace folders or for folders you do not currently need. Cloaking is useful when you are working with files from two or more branches under a common parent to prevent you from copying files unnecessarily. Finally, cloaking increases performance bandwidth and conserves local disk space by preventing folders and files not used currently from being copied to the local working folder. Today I noticed that I am missing the cloak option for a specific folder. I couldn’t find the reason, because it available for another Folder in same workspace. Later I found that it was because of the mapping of local and source folder are different. Like my TFS path was $Projects/System/Data/Binaries, it should be mapped to C:\Projects\System\Data\Binaries, but I was mapped to some other folder like C:\Projects\System\Data\DataBinaries. And then I changed it via File > Source Control > Workspaces option. After this I got the cloak option.

Cloak option of Source control explorer conext menu

You can more information in MSDN : Rollback Command (Team Foundation Version Control)

If you want to rollback you change 123, you need to do some thing like

cd c:\Code\you must useProjectName
tf rollback /changeset:123

1. Open Visual Studio 2010
2. Select Tools > Options menu.
3. Select the Source control Tab in the left side.


Source control options in Visual Studio options

4. Click the “Configure User Tools” button in the right pane. It will popup a Configure user tools dialog like this.


Configure user tools dialog

5. Now you are ready to enter the configuration for whichever tool you choose to use. Below is the settings for Beyond Compare.


Settings for Compare tool

6. Here is the settings.

Extension: .*
Operation: Compare
Command: C:\Program Files\Beyond Compare 3\BC2.exe [replace with the proper path for your machine]
Arguments: %1 %2 /lefttitle=%6 /righttitle=%7

Happy programming

Here is a detailed post regarding diff/merge configuration in Team Foundation – common Command and Argument values from James Manning.

Build Notification tool is now part of TFS product itself. So, it has been removed from Powertools.

Start Menu > All programs > Microsoft Visual Studio 2010 > Team Foundation Server tools > Build Notifications.

TFS Build Notification Tool