Skip to main content

TechEd 2009 Berlin: Microsoft has Acquired the Teamprise Client Suite

One of the great stuff that Microsoft announced during the TechEd 2009 conference at Berlin was the acquisition of the Teamprise Client Suite from Teamprise. With this step heterogeneous development on the Team Foundation platform became once again easier. Free upgrades will be provided for all customers who are using Teamprise today.

Teamprise Client Suite consists of 3 components:

  • Eclipse plugin - Allows developers to perform all of their source control, bug tracking, build, and reporting operations from within Eclipse and Eclipse-based IDEs, such as Rational Application Developer, JBoss, BEA Workshop, and Adobe Flex Builder. It integrates into the menu system of Eclipse as a standard Team Provider plug-in, but also provides developers with specific views and forms for interacting with the Team Foundation Server. Developers using the Teamprise Plug-in for Eclipse have the ability to take part in the entire software development process in use by their organization without leaving the comforts of their development environment.
  • Stand-alone Explorer - Combines all of the functionality available to Eclipse developers using the Teamprise Plug-in into a stand-alone, cross-platform GUI application for team members working outside of a development IDE. Perform source control operations, browse the Team Foundation Server repository, edit bug reports, run work item queries, monitor builds, and view project reports all from within an application that has a native look and feel on the operating system you are using.
  • Command line client - Provides a cross-platform, non-graphical interface to Microsoft's Team Foundation Server, for scripting and build scenarios or for developers who prefer a command-line interface. The command line interface is compatible with the current Microsoft supplied command line interface so scripts are interchangeable.

All of these components work on Windows, Mac, Linux and several flavors of Unix. In addition work is being done to explore providing these capabilities in mainframe environments to enable access to the Visual Studio ALM platform from there as well.

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