Skip to main content

TFS 2010 update available

Microsoft released an update (KB 983578) for:

  • Team Foundation Server 2010
  • All Team Explorer 2010 clients

Although it is called the Lab Management update it not only contains features for Lab Management but also for other TFS components.

What's in the upgrade?

Enables Visual Studio 2010 Lab Management functionality

  • Improves performance for Lab Management Workflow Wizard.
  • Improves performance for running automated test cases on Network Isolated Lab environments.
  • Fixes an issue in which a Test Controller service account that is the same as a Lab Service account causes issues with environment capabilities.
  • There is a new Expression Encoder 4.0 based Video Diagnostic data adapter to collect video recording when you perform tests. This diagnostic adapter replaces the Windows Media Encoder base video diagnostic adapter.

Install/Upgrade

  • Labels created in TFS2008 do not contain items after migration to TFS 2010 under certain rename/delete conditions.
  • TFS Cannot be re-installed (ATOnly) targeting a database that was patched before.
  • Tfs2010Beta2ToRTM operation is not executed when RC database is upgraded by post RTM server (RTM + Patch1 or SP1).

TFS Build

  • VS2008 “smart device” projects pick up the 2010 MSTEST rather than the 2008 one.
  • Unavailable build agents are pinged indefinitely rather than giving up after an hour.
  • Duplicate changeset listings in build report.
  • Test results for VS2008 solution not published in case of a failed test.
  • Cannot delete build drops if a controller goes down
  • Open Process File Location” grayed out on menu- right click on a build definition when connected to a TFS 2008 server

Version Control

  • Branch from label has been removed in TFS 2010 – now it’s back.
  • Convert folder to branch on a hierarchy root folder with children and cycle renames crashes VS.
  • Unshelve reports bogus errors about a null DownloadUrl when dependent renames are shelved and child item names overlap.
  • Incorrect query plan on QueryPendingChanges when querying all users pending changes can lead to bad performance.
  • merge /discard in both directions causes unnecessary “empty” merges in future merge attempts.
  • Issue in merge causes a conflict not to be generated when there is a rename in the target and source.
  • Overly aggressive automatic detection of file encoding can result in inappropriate encoding mismatches during merges.

Work Item Tracking

  • Work item queries containing references to deleted fields can cause a red X on the work items node.

Team Web Access

  • Firefox Browser: "Link Selected Items to a New Work Item" and other dialogs don't launch pages successfully
  • Chrome Browser: Adding an attachment doesn't work
  • Chrome Browser: Select Query Dropdown doesn't work in Choose Work Items window
  • Chrome Browser: Retain/Delete a build in Build Report page will get an exception “Unexpected callback response”
  • Query Picker Web Part Incorrectly Renders List Items (Rows) in List View (Overflow DIVs) within WebKit-based Browsers (including Safari, Chrome, etc)

The upgrade applies to

  • Visual Studio 2010
  • TFS Application Tier
  • Team Explorer 2010
  • Microsoft Test Manager (MTM)
  • TFS Build Controller
  • TFS Build Agent
  • TFS Test Controller
  • TFS Test Agent
  • TFS Lab Agent
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