Explanation:

All my source files where partial while performing TFS version control "get latest" operation on Windows Server 2008 R2 OS

 Solution:

Open Visual Studio with "Run as Administrator" option

Explanation:

You are opening a solution made in Visual Studio 2010 with VS 2012.  When you run Code Analysis you get a series of CA0053 errors, saying it is unable to load the rule sets from the Visual Studio 2010 directory

In the Error window you get an error message saying “Code Analysis detected errors.” And in the Code Analysis window you will get the “CA0053 Error running code analysis” with its “Unable to load rule assembly”.

This means the project is bound to Visual Studio 2010, where it should have been Visual Studio version independent. The absolute path to the Visual Studio 10 binaries is what causes the problem.

What has happened was that this certain VS2010 specific information was “inadvertently” introduced in SP1, and it has not been fixed in any later update. It does NOT happen if you run in Debug|x86 or Release|x86, but any other configuration you have added will give you this error.

Solution:

Tool to fix the errors available at http://visualstudiogallery.msdn.microsoft.com/471da13b-d415-4a44-a4e9-a8222316b902

Explanation:

A regular get operation will deleted each item in the target workspace folder and re-downloaded the folders and files from the server to target workspace folder.

Solution:

Use remap switch with tf get command

"tf get /remap"

Note: /remap switch does increase the load on server to process your request

Explanation

A lock cannot exist in a shelveset, When you try to lock an item and shelve it, your lock will be removed as part of the shelve operation.

Explanation:

Multiple users mapping their workspaces to same folder on shared drive lead to conflicts in performing checkin, Checkout and "get latest" operations.

Workaround:

You can try users mapping their workspaces to different folder on shared drive.

For example

user 1 -- <Shared Drive>\User 1 Workspaces\

user 2 -- <Shared Drive>\User 2 Workspaces\

user 3 -- <Shared Drive>\User 3 Workspaces\

user 4 -- <Shared Drive>\User 4 Workspaces\

Note: Mapping the workspace to a shared drive lead to bad performance.