21

I see that PowerCommands for Visual Studio 2010 supports visual studio 2012, but it was last updated in Aug 2010. Is there a new "PowerCommands for Visual Studio 2012" or is there a viable replacement?

Guilherme Fidelis
  • 1,022
  • 11
  • 20
Francois Nel
  • 1,662
  • 2
  • 19
  • 29

5 Answers5

31

You don't need a replacement. If you install the Power Commands again, from within VS 2012 (Tools -> Extensions and Updates), it will be applied to VS 2012.

From here:

Just reinstall, even if you already have it for VS2010. The reinstall will then apply it to VS 11

I just did it, and it worked perfectly.

Edit

Productivity Power Tools

Microsoft Visual Studio Team Foundation Server 2012 Update 1 Power Tools

For Visual Studio 2013, it looks like Power Commands is now part of Power Productivity Tools.

Bob Horn
  • 33,387
  • 34
  • 113
  • 219
2

I ended up using VSCommands for Visual Studio 2012. This tool provided all I needed from PowerCommands and more.

Francois Nel
  • 1,662
  • 2
  • 19
  • 29
0

Most of what was in the Productivity Power Tools are now part of VS 2012. There are a few items missing, afaik, what are you looking for in particular ?

Terje Sandstrøm
  • 1,979
  • 15
  • 14
  • I'm looking for the feature of vertical tabs at the left side and the enhanced scrollbar. – Konrad Sep 10 '12 at 14:40
  • 1
    what are the features that are now part of VS 2012? I like the feature that allow you to open a file (in the solution explorer) in the directory it resides. Also, the feature that allows you to collapse all nodes in the solution explorer. I found [VSCommands for Visual Studio 2012](http://bit.ly/PYmtXa) that gave me the same and more. – Francois Nel Sep 11 '12 at 06:10
  • @FrancoisNel Collapse all nodes is in 2012 I believe – jamiebarrow Sep 20 '12 at 14:46
0

As mentioned on the Productivity Power Tools 2012 page, the Power Commands were added to that addon.

Jean Hominal
  • 16,518
  • 5
  • 56
  • 90
0

Download the VS2010/2012 version from the VS Gallery.

Unzip the .vsix to a folder (i.e. using the great 7zip), it's just a zip file.

Edit the extension.vsixmanifest file and add this element after the 11.0 one:

  <VisualStudio Version="12.0">
    <Edition>Pro</Edition>
  </VisualStudio>

Repeat for every future version of VS that comes out ;)

Now re-zip the contents (files, not the root folder, so that the extension.vsixmanifest is at the root of the zip file, not within a folder), rename the zip file to .vsix, and double-click to install to all your newly supported editions.

Enjoy!

kzu
  • 1,795
  • 15
  • 16