Skip to main content

Just announced: TFS Express

Just before the availability of  VS/TFS 11 Beta, Microsoft introduces a new download of TFS, called Team Foundation Server Express, that includes core developer features:

  • Source Code Control
  • Work Item Tracking
  • Build Automation
  • Agile Taskboard
  • and more…

It’s a FREE version of TFS for individuals and teams of up to 5 users.

The Express edition is essentially the same TFS as you get when you install the TFS Basic wizard except that the install is trimmed down and streamlined to make it incredibly fast and easy. In addition to the normal TFS Basic install limitations (no Sharepoint integration, no reporting), TFS Express:

  1. Is limited to no more than 5 named users.
  2. Only supports SQL Server Express Edition
  3. Can only be installed on a single server (no multi-server configurations)
  4. Includes the Agile Taskboard but not sprint/backlog planning or feedback management.
  5. Excludes the TFS Proxy and the new Preemptive analytics add-on.

More users can be added by buying Client Access Licenses (CALs) for the additional users. And even upgrading to a full TFS license is supported without losing any data.

Another thing I noticed is that Microsoft finally enabled TFS integration in their Visual Studio Express products. The Visual Studio Express client integration with work with any Team Foundation Server – including both TFS Express and the Team Foundation Service. No excuses left to not start using TFS.

Installation of TFS Express will be done by just clicking on a link, running the web installer and you’re up and running in no time.

Maybe there will be a free version of Team Foundation Service too?

And here is the link to the official blog post by Brian Harry: Coming Soon TFS Express.

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.

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) ...