locked
TFS 2012 - Windows Shell Extensions not working with Comment and Work Item Policies RRS feed

  • Question

  • We are running TFS 2012 and VS 2012 Pro.  Once we upgraded to use the 2012 Power Tools' windows shell extensions, we had the two check-in policies start failing.  On our machines we still have VS 2010 and the 2010 Power Tools installed (without the shell ext.)

    The new windows ext. are failing with the following errors:

    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:

    Error loading the Work Items policy (The policy assembly 'Microsoft.TeamFoundation.VersionControl.Controls, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' is not registered.). Installation instructions:


    These policies are working fine in VS 2010 and in VS 2012.  These errors only show up when performing a check-in using the shell extensions.   From what I've read, these policies were rolled into the actual product and are not distributed in the power tools. 

    Does anyone have any thoughts on this?


    Wednesday, October 17, 2012 9:12 PM

Answers

  • David, the team tells me they plan to fix this bug for the next power tools release (I believe there will be one in the same timeframe as the VS Update 1 release).

    http://blogs.msdn.com/buckh

    • Marked as answer by David_Stanley Tuesday, October 23, 2012 1:44 PM
    Tuesday, October 23, 2012 1:41 PM
    Moderator
  • I have verified that Microsoft Visual Studio Team Foundation Server 2012 Update 1 Power Tools (dated 11/29/2012) corrects the issue.

    http://visualstudiogallery.msdn.microsoft.com/b1ef7eb2-e084-4cb8-9bc7-06c3bad9148f

    • Marked as answer by David_Stanley Friday, November 30, 2012 3:23 PM
    Friday, November 30, 2012 3:23 PM

All replies

  • Hi David,

    Thanks for your post!

    Can you tell me what edition of the TFS 2012 Power Tools do you installed, that's a known issue which is resolved in the final release of the TFS 2012 Power Tools. Please download from the following link:

    http://visualstudiogallery.msdn.microsoft.com/b1ef7eb2-e084-4cb8-9bc7-06c3bad9148f

    The error you are getting is related with TFS 2012 using the comment policy form the TFS 2010 Power Tools.

    Can you by removing this check-in policy and re-add it with the TFS 2012 Power Tools, it used the lastet version , which is compatible with VS 2012. 

    For more information, please refer to http://stackoverflow.com/questions/9535256/visual-studio-11-power-tools-checkin-policies

    Hope it helps!

    Best Regards,


    Cathy Kong [MSFT]
    MSDN Community Support | Feedback to us

    Thursday, October 18, 2012 8:25 AM
    Moderator
  • Thanks for the reply Cathy.

    The version of power tools you listed is what we are running, but just to be sure I downloaded a new copy and uninstalled/reinstalled it.  I also went into VS 2012 as I had done before and removed the check-in policies and re-added them.

    I then tried to perform a check-in from the tfs 2012 windows shell extension and received the same errors.  It is still trying to use the 10.0... version of the check-in policies.

    Thursday, October 18, 2012 1:28 PM
  • Hi David,

    Thanks for your feedback!

    In the download page of TFS 2012 Power Tool: http://visualstudiogallery.msdn.microsoft.com/b1ef7eb2-e084-4cb8-9bc7-06c3bad9148f Please select Q And A page, this issue is discussed there.

    I think you can post the issue there for better response.

    And I am also looking into this issue and will give you an update as soon as possible.

    Thank you for your understanding and support.

    Best Regards,


    Cathy Kong [MSFT]
    MSDN Community Support | Feedback to us

    Friday, October 19, 2012 8:50 AM
    Moderator
  • David, the team tells me they plan to fix this bug for the next power tools release (I believe there will be one in the same timeframe as the VS Update 1 release).

    http://blogs.msdn.com/buckh

    • Marked as answer by David_Stanley Tuesday, October 23, 2012 1:44 PM
    Tuesday, October 23, 2012 1:41 PM
    Moderator
  • Okay, thanks Buck.
    Tuesday, October 23, 2012 1:44 PM
  • I have verified that Microsoft Visual Studio Team Foundation Server 2012 Update 1 Power Tools (dated 11/29/2012) corrects the issue.

    http://visualstudiogallery.msdn.microsoft.com/b1ef7eb2-e084-4cb8-9bc7-06c3bad9148f

    • Marked as answer by David_Stanley Friday, November 30, 2012 3:23 PM
    Friday, November 30, 2012 3:23 PM