Comments
2 comments
-
The likely cause of this is that the policy is set up for a version of Team Explorer that SQL Source Control isn't using. You should be able to resolve this following http://documentation.red-gate.com/display/SOC7/The+Team+Foundation+Server+for+this+workspace+does+not+support+one+or+more+of+the+checkin+options+you+have+selected#TheTeamFoundationServerforthisworkspacedoesnotsupportoneormoreofthecheckinoptionsyouhaveselected-HowtoconnectwithoutusingTeamExplorer.
However it's also worth noting that Microsoft did not ship TFS powertools with VS 2017 so if you are using that and don't have VS2015 installed as well you can encounter problems. -
It does not work with TFS 15.117.27024.0. Does it work at all with TFS?
Add comment
Please sign in to leave a comment.
Hi all
I've just enabled the forced comments in Visual Studio for when we commit changes to TFS.
This should also work in SSMS for when we make changes to a database and try to commit those changes.
Unfortunately, even when I add a comment, I get the following error:-
Internal error in Changeset Comments Policy. Error loading the Changeset Comments Policy policy (The policy assembly 'Microsoft.TeamFoundation.PowerTools.CheckinPolicies.ChangesetComments, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' is not registered.). Installation instructions:
I've reported it using the "report issue" option on the error message but wondered if anyone else had come across this?
Regards
Richard