Internal error in comments of changes to the change policy after updating VS2015 to update 1

Question

Everything was all right about an hour ago, when I tried to check something, political friendship reminded me of "provide a comment for registration." Then I installed VS2015 Update 1, like some of my colleagues, and after that I get the following error message when I try to check something in:

Internal error in change comment policy. Error loading policy of change comment policy (assembly policy "Microsoft.TeamFoundation.PowerTools.CheckinPolicies.ChangesetComments, Version = 10.0.0.0, Culture = neutral, PublicKeyToken = b03f5f7f11d50a3a" is not registered.). Installation Instructions: To install this policy, follow the instructions in CheckForComments.cs.

My colleagues, of course, do not. As far as I know, after VS2012, there is no need to install any version of Power Tools, so why is this happening? In addition, I also have VS2013 installed, where I DO NOT get this error message, this version works fine. Does anyone have an idea where I need to look?

Answer 1

OK I understood. Somehow, the installation ruined something. Folder on my machine

C: \ Program Files (x86) \ Microsoft Visual Studio 14.0 \ Common7 \ IDE \ CommonExtensions \ Microsoft \ TeamFoundation

was pretty empty where my colleagues had a connection leading to this folder

C: \ Program Files (x86) \ Microsoft Visual Studio 14.0 \ Common7 \ IDE \ Extensions \ XXXXXXX

where XXXXXX obviously varies from machine to machine. To find the right one, go to the extensions folder (one up) and find the one that contains "Microsoft.TeamFoundation.Build.Controls.dll" and some other Teamfoundation DLLs, then open the extended command line and create the missing node like this:

mklink /j "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer" "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\XXXXXX" 

(note, you need to replace XXXXX with the name of the folder on your computer)

- NOTE. Please do not forget RESTART Visual Studio after this change to start ironing smoothly.