maintaining TFS workspace on Machine Name change

If your Build machine name changes, you will not be able to use your old workspace in TFS.

In that case you can recover the same by updating TFS using /updateComputerName switch.

This Instructs Team Foundation to update its tables to reflect a change in the name of a client computer. If you specify this option, you must also specify a team project collection by using the /collection option.

"C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\TF.exe" workspaces /collection:http://myserver:8080/tfs/DefaultCollection  /updateComputerName:OldComputerName

Ex:

"C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\TF.exe" workspaces /collection:http://tfsRVN:8080/tfs/RAHULN_Others /updateComputerName: RAHULN

Setting up Visual Studio 2012 for SharePoint 2013

In a clean server, the user must be installing Visual Studio 2012 and Sharepoint 2013 for developing Sharepoint applications.

But once you open you will notice that there is no option in Visual Studio 2012 to create Sharepoint project\applications.

To get the sharepoint templates into Visual Studio, you need to install Microsoft Office Developer Tools for Visual Studio 2012

But for this, we require Microsoft Web Platform Installer and unfortunately, this won’t be available in restricted internet access of our environment.

So download and install Microsoft Web Platform Installer.

And from this we can install Web Developer Tools, in case it’s not available, download Microsoft ASP.NET and Web Tools 2013.1 RC (web developer Tool) and install prior to Microsoft Office Developer Tools for Visual Studio 2012

But If you try to create a SharePoint 2013 project and you get the following error message:

Error

“An error occurred while trying to load some required components.

Please ensure that the following prerequisites components are installed:

Microsoft Web Developer Tools

Microsoft Exchange Web Service.”

The problem is that the Microsoft Web Platform Installer adds parameters when installing the Microsoft Exchange Web Services that must be used in order to get around the error. If you have already installed the Microsoft Exchange Web Services, uninstall it from Control Panel and then open up a command prompt

Run command as:

EwsManagedApi.msi addlocal="ExchangeWebServicesApi_Feature,ExchangeWebServicesApi_Gac"

Download msi for Microsoft Exchange Web Services API 2.0 and Open command prompt