Explanation:

VS 2012 update 3 failed to install on Windows 7 64 bit OS due to Microsoft Root Certificates

Exception: 

"Microsoft Root Certificate Authority 2010 or 2011 is missing and can cause installation failures for some signed packages.  For more info, see http://support.microsoft.com/kb/931125."

Solution:

• Go to this page http://www.microsoft.com/en-in/download/details.aspx?id=38918
• Download and run rootsupd.exe

Note: You may see "Update for Root Certificates For Windows XP" in the site page. But the executable work on win 7 and also fix the issue.

• Try to install VS 2013 Update 3 again.

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

Solution:

vs_ultimate.exe /uninstall /force

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:

TFS 2012 and VS 2012 featured with new workspace concept called “local” workspaces.The workspace concept which was available from VS/TFS 2005 - 2010 is called as “server” workspaces. “server” workspaces is the default option while creating a new workspace in VS 2012.

When a local workspace is created, the required data structures will be moved from the TFS server onto the TFS Client. The data structures are local to local machine instead of being hosted on the TFS server. Moving the data structures to local machine gives VS 2012 the ability to perform a number of source control operations without TFS web service calls or active connection to TFS server. The following operations continue to work when the local machine is disconnected from the TFS server.

• Opening a source-controlled solution
• Checking out a file for edit
• adding a new file or folder for add
• Delete on an existing file or folder
• Rename on an existing file or folder
• Monitor pending changes in the workspace
• Undoing pending changes
• Diffing your copy of a file with the version of the file your change is pended against
• The local workspace will not carry read only bit during get source.
• “Promoting” the candidate adds and/or deletes
• The local workspace will be invisible to VS 2010 and earlier versions
• No enforcement of PendChange permission or checkout locks
• The local workspace can be converted to Server workspace and reverse the same

Drawback on Local workspaces.

Local workspaces have scalability limitations due to their use of the local workspace scanner which checks for edited items.If the workspace has more than 50,000 items, There may be performance problems or "TF400030 errors as operations exceed 45 seconds in duration." may occur

Steps to create a local workspace.