How to set Microsoft.TeamFoundation.VersionControl.Controls to TFS2017

• 
  Hi @DanielJ ,
  
  Which version of Team Explorer did you install? Have you tried to connect without using Team Explorer?

  Tianjiao_Li November 01, 2017 11:19

  - 0 +
• 
  We are using TFS 2017 and I have Visual Studio 2017 professional installed which is 2017 explorer.
  
  Yes, I did find that as well but received the same error as my first attemt.
  The error I receive is:
  Internal error in Work Items. Error loading the Work Items policy (The policy assembly 'Microsoft.TeamFoundation.VersionControl.Controls, Version=10.0.0.0, Culture=neutral, PublicKeyToken=' is not registered.). Installation instructions:
  
  
  Also just to verify that my VS instance can check into the TFS source control, I removed Redgate source control link within SSMS to remove any locks, connected to my db repo within VS 2017 team explorer, checked out and made my change to a static table, then was able to check in successfully.

  DanielJ November 01, 2017 18:30

  - 0 +
• 
  Sorry to not confirm earlier that as SQL Source Control relies on TFS Power Tools, you have to install VS2015 (or older) alongside VS2017 as there is no release of any Power Tools for VS 2017 yet.

  Tianjiao_Li November 06, 2017 14:34

  - 0 +
• 
  Is the same requirement true if you're using Git integration with TFS vs. TFVC?
  
  I ask because right now we're using TFVC integration for these databases. Will ultimately be moving to Git integration, so my hope is that is the difference and we're not tied to having both versions of Visual Studio installed as a work-around.

  Cogbeard November 08, 2017 16:45

  - 0 +
• 
  Hi @Cogbeard ,
  
  SQL Source Control will work with TFS and VSTS (GIT or TFVC) without power tool as long as you don't use TFS policy.

  Tianjiao_Li November 10, 2017 16:14

  - 0 +
• 
  Is there a fix for this yet?

  mhhassan February 15, 2018 13:22

  - 0 +
• 
  We have the same issue and would like to avoid having our developers install Visual Studio 2015 - is there any other workaround at this time?

  Aadler January 22, 2020 19:08

  - 0 +
• 
  @Aadler @mhhassan
  
  Could you confirm if connect without using Team Explorer helps?
  
  Thanks!
  
  

  Tianjiao_Li January 27, 2020 12:08

  - 0 +
• 
  What ended up working for us was setting "IgnoreTfsPolicies" in the RedGate_SQLSourceControl_Engine_EngineOptions.xml:
  

  <EngineOptions version="3" type="EngineOptions">

    <IgnoreTfsPolicies>True</IgnoreTfsPolicies>

  </EngineOptions>
  
  Installing VS2015 also worked where that was an option (based on disk spaces and other considerations)

  Aadler January 28, 2020 17:22

  - 0 +
• 
  @Aadler
  
  It looks like Microsoft has integrated most features of the TFS Power Tools into Visual Studio 2017. The Shell extensions for 2017 have been released separately Please feel free to give it a go.
  

  Tianjiao_Li January 29, 2020 10:32

  - 0 +

Add comment

Please sign in to leave a comment.