The free option I’ve selected is ExtractNow, which you can download from here:Ĭlick on the “Download ExtractNow!” link on the bottom of the page and run the installer.

We won’t burn the image to a DVD (the only reason I could see why you’d want to do that is if you want to make multiple installs, but you might as well extract the ISO to a network share). There are several options to extract or burn an ISO, but I’ll use a free one here. Now that you have the IMG file, we can extract it. Oh, by the way, to be clear, you do *not* need a version of Visual Studio on the box to install Team Explorer, it is a standalone application, but if you do have one, it will integrate with it. So you probably have time for a cup of coffee or two, trip to Seattle’s Best included.

At 387.4 MB it’s a pretty big download (especially when compared with this) but it does contain the Visual Studio shell, which explains it, kind of. Just click on the “Download” button and store the file in a local temporary folder. I wasn’t completely satisfied with the explanation (it’s still a bad customer experience) but at least there is hope as the plan is to make it a lot smoother with Visual Studio 2010. I asked the team why they made that weird and less than optimal choice, and apparently there are some technical reasons why a simple msi wouldn’t work. The first and main problem here is that Team Explorer, while free, comes in a very unfriendly format: an ISO image of the DVD. Over the past few years, I’ve been managing a number of small and large projects on CodePlex, and while the Subversion bridge has provided a much needed simple choice of client software, TFS remains its native protocol, which makes it still very much relevant to people who do a lot of work there.īut as I said, installing the client software may be challenging. One of the challenging aspects of working with TFS as your source control system is very unfortunately the installation of the client software.

Tfs client tools 2010