Onward and Upward

Blog archive

TFS Power Tools Updated With Support for VS 2012 Update 2

Microsoft has updated its Power Tools, a suite of enhancements for Team Foundation Server (TFS) projects, to work with Visual Studio 2012 Update 2.

Now, those of you paying close attention to the Visual Studio team's constant stream of updates may wonder why Power Tools is now being updated to support Update 2, when Update 3 was just released as a go-live production Release Candidate (RC). Microsoft Technical Fellow Brian Harry, on his blog, chalks it up to taking "longer than we had hoped" to prep the Power Tools.

But Harry goes on to explain that new Power Tools update (officially called TFS 2012.2 Power Tools update) includes a change that should bring it fully in line with the new Visual Studio release method of frequent, incremental updates instead of infrequent, service-pack-level updates every year or two as in the past. Harry writes:

"Our Power Tools setup has traditionally had a block to prevent it from working with the next version of VS (which is why the Power Tools from Update 1 wouldn't work with Update 2).  This is a bit of a hold-over from before we started doing the regular update cadence.  At that time, it was pretty likely that we'd change something in the 2 years between updates that would break the Power Tools and we'd work hard to have new releases of Power Tools ready before the final release of VS/TFS."

The block has been removed, and Harry says "we fully expect" that this latest revision will work with Update 3. In fact, he's installed it on his version of VS 2012.3 (i.e. Visual Studio 2012, Update 3 -- the RC) and he says it's working well. Of course, your mileage may vary, so tread carefully.

Harry added that there are no significant changes in the new version of Power Tools; just some bug fixes and the removal of the "back/restore" Power Tool. The main reason for the release was because, Harry says, Microsoft heard from "a number" of its TFS customers that they uninstalled VS 2012 Update 2, rather than give up their Power Tools.

This is why it's good to bring your complaints to Microsoft. There remains a perception that large companies don't listen to their customers; or even if they do, that making changes to products in response to those complaints takes forever and a day. This Power Tools update shows that, at least for the Visual Studio/TFS teams, they are listening; also, that the new, agile release methodology is paying dividends.

Posted by Keith Ward on 05/08/2013 at 1:15 PM


comments powered by Disqus

Featured

  • Creating a Progressive Web App with Blazor WebAssembly

    Not surprisingly, it's dead easy to create an app in Blazor that runs outside of the browser window and (potentially) in an offline mode. Before you get carried away, though, there are some key design decisions to make.

  • GitLab Takes Over VS Code Extension, Plans Improvements

    DevOps specialist GitLab has officially taken over the control of a GitLab extension for Microsoft's open source, cross-platform Visual Studio Code editor.

  • VS Code Python Tool Now Does Native Notebooks

    The Python Extension for VS Code Insiders team is previewing the newest implementation of notebooks, used frequently in data science with offerings such as Jupyter Notebooks.

  • As .NET 5 Nears, Content/Documentation Reorganization Starts

    A GitHub project is seeking to reorganize documentation and developer content in advance of the November debut of .NET 5, a unification of all things .NET that combines. .NET Core and other components.

  • Windows Devs Get Cross-Platform Page, Issues Repo

    Developers doing their coding on the Windows OS have received two new resource gifts from Microsoft: a new landing page for those using cross-platform technologies and a new GitHub repo with which to report issues to Windows engineering teams.Developers doing their coding on the Windows OS have received two new resource gifts from Microsoft: a new landing page for those using cross-platform technologies and a new GitHub repo with which to report issues to Windows engineering teams.

.NET Insight

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.

Upcoming Events