WOW!!! what a release!!!

We have a LOT of new staff released this week…

The Release list for this week and three more important Releases:

• TFS 2010 SP1 – My post on this release: “Visual Studio 2010 SP1 and TFS 2010 SP1–What’s New? (Summary)”, Public Download
• Visual Studio 2010 SP1 - My post on this release: “Visual Studio 2010 SP1 and TFS 2010 SP1–What’s New? (Summary)”, Public Download
• Load Test Feature Pack - Gives you unlimited Virtual Users in Visual Studio Ultimate Edition, on that in my next post, MSDN Download Page
• Project Server Feature Pack – My post on this subject: "Team Foundation Server 2010 (TFS) and Project Server Integration Is Now Available In Beta", MSDN Download Page
• Power Tools – My post on this release: “New TFS 2010 Power Tools Are Available! (March 2011 Power Tools)”
• Team Explorer Everywhere SP1 – My post on this release: “Team Explorer Everywhere 2010 SP1 Release Version Is Available”
• Feature Pack 2 - My post on this release: “Feature Pack 2–Testing pack Is Available”

As you can see we have a lot of staff, what do we do with all these releases?, where do we install each of the releases?

Luckily Brian Harry came to the rescue with hi post: “Installing all the new stuff”

Note: For your convenience I have copied the most important parts of his post.

Have Fun!!!

On the client

Other than the restriction that you must install VS before any of the other things, there really aren’t any ordering requirements.  I’ve seen requests to enable “slipstreaming” of 2010 and 2010 SP1 – that’s creating a combined installer that installs both the RTM product and the SP1 together in a single installation experience.  Unfortunately, we are not going to be able to do that this release.  I won’t bore you with all the details but let’s just say that our install is complicated enough that it’s not easy and our infrastructure doesn’t support it well.  Getting into a position where this is something we can do as a matter of course is something we are striving for in our next release.

• VS 2010 and/or Microsoft Test Professional 2010
• VS 2010 SP1
• Team Explorer Everywhere 2010 with SP1
• Testing Feature Pack (includes Architecture & Modeling Feature Pack)
• Power Tools
• Windows SDK – beware that there’s an issue documented here.

On the TFS server

If TFS and VS are on the same machine they the must either both be updated to SP1 or neither.  We don’t support mixing SP1 and non-SP1 on the same machine.

• TFS 2010
• TFS 2010 SP1
• Make sure you upgrade your build machines to SP1 too – while not strictly necessary, it’s highly recommended.

On a Sharepoint Server associated with TFS

The Sharepoint Extensions for TFS need to be patched.  There was at least one very significant performance fix.

• TFS 2010 SP1

On a TFS Build Machine

• TFS 2010 Build Controller/Agent(s)
• TFS SP1
• VS SP1 (assuming you have VS installed on your build machine too – most people do).

On Project Server

• Ensure that TFS 2010 SP1 is installed on your TFS server
• Project Server Integration Feature Pack

On a Test Controller/Agent

• Test Controller/Agent Software (available at http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=a3216d2a-0530-4f6c-a7c9-0df37c54a902)
• VS 2010 SP1
• Virtual User License Key (available on your MSDN Subscriber Downloads) installed in the Test Controller config UI

On a TFS Proxy

To my knowledge, we didn’t actually make any SP1 fixes for the proxy so, in general, you shouldn’t need to install SP1.  If, however, the Proxy is installed on a machine with VS and you install VS SP1 then you will need to install TFS SP1 as well.  Consistency is required on the same machine.

• TFS Proxy
• TFS SP1