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

DanielJ

So I just got a new computer that does not have any other version of Visual Studio other than 2017. I have installed SSMS 2017 to connect to our database and setup Redgate to connect to our TFS2017 instance.

I am getting the following error when trying to check-in changes:
nternal 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:

I went to the link and it is requesting VS2012 instance or install the 2012 TFS power tools.This, I do not want to do.

I then found this link to override Source Control engine to use a specific version of TFS here:
https://documentation.red-gate.com/soc6/troubleshooting/error-messages/the-team-foundation-server-for-this-workspace-does-not-support-one-or-more-of-the-checkin-options-you-have-selected

Sweet, so I set my engine up to use TFS2017.

Error now:
To use this database with SQL Source Control, you must have Team Explorer installed. This is installed with Visual Studio. If you have Team Explorer 2013 or later, you also need to either use SQL Server Management Studio 2012 or later, or install an earlier version of Team Explorer (eg Team Explorer 2012). You don't have to uninstall Team Explorer 2013.

I do have Team Explorer installed but somehow it is not seeing it. I need to be able to use Redgate with VS2017 without having to use 2012 power tools. Has anyone run into this?

Tianjiao_Li

Hi @DanielJ ,

Which version of Team Explorer did you install? Have you tried to connect without using Team Explorer?

DanielJ

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.

Tianjiao_Li

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.

Cogbeard

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.

Tianjiao_Li

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.

mhhassan

Is there a fix for this yet?

Aadler

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?

Tianjiao_Li

@Aadler @mhhassan

Could you confirm if connect without using Team Explorer helps?

Thanks!

Aadler

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)

Tianjiao_Li

@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.