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.

Labels:

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         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...
Read more