This project has moved. For the latest updates, please go here.


Could not load type KnownCapFlagsScc


After installing this extension I cannot connect to my TFS 2013 server from VS2015 and get this error message:
Could not load type 'Microsoft.TeamFoundation.Client.KnownCapFlagsScc' from assembly 'Microsoft.TeamFoundation.Client, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
Closed Jul 24, 2016 at 8:11 AM by deadlydog
I believe this issue has been fixed. If not, please open a new issue on the GitHub website at


deadlydog wrote Apr 9, 2016 at 11:41 PM

Thank you for reporting this issue. Could you please provide me with a little more info. Do you only have VS 2015 installed, or other versions of VS as well?

If you navigate to the VSDiffAllFiles extension directory, does it have the Microsoft.TeamFoundation.Client.dll? It should. e.g. on my machine the DLL is located at "C:\Users\Dan.Schroeder\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\u1psfdzh.0bf\Microsoft.TeamFoundation.Client.dll". Of course the username and random directory name at the end will be different on your machine. You'll know your in the right directory though because there should also be a VS.DiffAllFiles.VS2015.dll file.

deadlydog wrote Apr 9, 2016 at 11:52 PM

I've also found this MSDN forum post of others experiencing the same error, so it looks like it may be a bug with VS that my extension brings forward for some reason. Still waiting on getting more info.

deadlydog wrote Apr 10, 2016 at 12:51 AM

Also, are you using VS 2015 with Update 1? Lots of people have reported seeing this same issue after installing VS 2015 Update 1. I have it installed though and do not have any problems.

scadwallader wrote Apr 12, 2016 at 2:04 PM

FWIW: I started seeing the issue with VS2015 Update 2 (no problems with Update 1).

I see the issue both with this extension enabled and disabled.

After multiple uninstall/repairs, the specific KnownCapFlagsScc issue went away but I see other ones like: System.TypeLoadException: Method 'CreateItem' in type 'Microsoft.TeamFoundation.VersionControl.Controls.PendingChanges.PendingChangesFileListViewHelper' from assembly 'Microsoft.TeamFoundation.VersionControl.Controls, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' does not have an implementation.

My hunch is there are issues with the TFS API DLLs.. and your extension may be affected because it utilizes them. I was going to run some diffs against a clean machine that's working fine and see if I could find anything in particular.

deadlydog wrote Apr 12, 2016 at 3:11 PM

Thanks for providing the information @scadwallader and taking the time to help investigate :)

scadwallader wrote Apr 12, 2016 at 3:32 PM

FWIW: The fix for me was running devenv /setup as an administrator.

scadwallader wrote Apr 12, 2016 at 3:46 PM

To be more explicit:
  1. Run "Developer Command Prompt for VS2015". If you are not running on an administrator account, be sure to right click and launch the application as an administrator.
  2. Type "devenv /setup"
Also.. more than glad to help. I really appreciate your tool. I was just about to go build it myself as part of my extension CodeMaid and was very pleasantly surprised to find someone else had already done it. :) Anxious for the git aspects when you get to them.. :)

deadlydog wrote Apr 12, 2016 at 4:49 PM

Awesome, thanks so much @scadwallader!

@carlin5cott, can you confirm if this fix works for you as well? Thanks.

carlin5cott wrote Apr 13, 2016 at 10:11 PM

Running "devenv /setup" did not fix the issue for me.

I'm using Visual Studio Enterprise 2015, Update 1.

carlin5cott wrote Apr 13, 2016 at 10:25 PM

I deleted all of the Microsoft.*.dll files in the extension folder and now everything works.

The extensions folder can be found by searching for VS.DiffAllFiles.VS2015.dll in C:\Users{your username}\AppData\Local\Microsoft\VisualStudio\14.0\Extensions.

I figured VS would know where to find the correct versions of all of the Microsoft libraries and that maybe this extension was using an incompatible library.

deadlydog wrote Apr 13, 2016 at 10:55 PM

Thanks @carlin5cott, that's very helpful. Do you have multiple versions of VS installed? Or just VS 2015?

If I remember correctly, way back when I first released the extension I had to include the Microsoft assemblies to make sure that it used the correct version. e.g. I had VS 2012 and 2013 installed, but it wouldn't work in 2012 because it always tried to use the 2013 assemblies. I might need to revisit this though.

carlin5cott wrote Apr 13, 2016 at 11:26 PM

@deadlydog: I only have VS 2015 but I installed Enterprise over the top of Professional.

That's interesting about the backwards compatibility issue. Maybe they're using the GAC for the assemblies rather than the currently running version of VS.

YiannisY wrote May 9, 2016 at 11:01 AM

For the fix was a combination of all the above :-)

My setup: Windows 10, VS2015 Enterprise 2015 14.0.25123.00 Update 2

The fix:
  1. Make sure VS is closed.
  2. Copy the following files:
    • Microsoft.TeamFoundation.Client.dll
    • Microsoft.TeamFoundation.Common.dll
    • Microsoft.TeamFoundation.Controls.dll
    • Microsoft.TeamFoundation.VersionControl.Client.dll
    • Microsoft.TeamFoundation.VersionControl.Controls,dll
    • Microsoft.VisualStudio.Services.Common.dll
      from C:\Program Files\Common Files\microsoft shared\Team Foundation Server\14.0
      to the extension folder (The extension folder can be found by searching for VS.DiffAllFiles.VS2015.dll in C:\Users{your username}\AppData\Local\Microsoft\VisualStudio\14.0\Extensions)
  3. Open command line console as admin and run devenv /setup
  4. Restart the fixed VS!
I hope it works for you also. It is a great tool by the way :-)

rafekemmis wrote Jun 23, 2016 at 2:54 PM

Greetings, I'm running into this exact same issue in my extension. Was wondering if this project was able to hunt down the cause of the exception. So far the only thing I've seen that might be the culprit is that the two users that experienced this both had an older version of VS installed along side of VS 2015. OS version and TFS server version don't appear to be the cause.

Here's our bug report for reference:



deadlydog wrote Jul 1, 2016 at 9:09 AM

Hey all, I've just uploaded a new v1.0.2 version of the VS 2015 extension. Can you please give it a try and let me know if the problem(s) seem to be fixed in this version, or if you still encounter an error please (and post the error). I haven't been able to reproduce any of these problems myself, so I was not able to test if the fix I put in actually works or not. Thanks.