Skip to main content

TFS 2010 Power Tools Released

After the release of TFS 2010, the TFS 2010 Power Tools couldn’t wait to follow. So we’ve got a new release of:

A few features are extended but the team didn’t add any really big new stuff.  An overview:

Process Template Editor (PTE)

The Process Template Editor now support all of the new 2010 features like link types, etc.  They also added GUI support for a few TFS process features that have been there all along. 

  • Support for defining link types
  • Support for work item type categories
  • Support for query folders
  • Support for new work item form controls: label, link labels, new links control
  • Support for adding build and lab template settings
  • Support for editing permissions on source control, build, lab, queries/query folders
  • Fixed 158 bugs

Team Members

  • Customized Instant Messaging settings
  • The ability to launch communicator by double clicking on the identity
  • More async operations (save settings)
  • Improved error handling (now in the output window).

Team Foundation Build Extensions

The Team Foundation Build Extensions provide the ability to execute Ant or Maven 2 builds from Team Foundation Server and publish the results of the build along with any associated JUnit test results back to Team Foundation Server.  This release is compatible with Team Foundation Server 2005, Team Foundation Server 2008 and Team Foundation Server 2010.

Alerts Editor

They made some small improvements to the Alerts Editor.

  • Moved from the team project tree in Team Explorer to a submenu item of the Team Project Collection. This change highlights the scope of the tool, which is at the project collection level, and reduces confusion between the projects alert and the old alerts node.
  • Simplified UI scheme and more default alerts around Team Build scenarios.

Portals And Reports

In TFS 2010, it’s possible to install Sharepoint but not Sharepoint portals and reports.  To add them later you can now use

  • tfpt addprojectportal - Create a project portal for an existing Team Project that doesn't currently have one.
  • tfpt addprojectreports - Create (or overwrite) the reports for an existing Team Project.

Best Practices Analyzer

And of course also some improvements in the Best Practices Analyzer.  TFS 2010 brings a lot of new capabilities that really changes the breadth and depth of health checks necessary.

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...