Everything you want to know about Visual Studio ALM and Farming
Brian Harry is a Microsoft Technical Fellow working as the Product Unit Manager for Team Foundation Server. Learn more about Brian.
More videos »
We released a ton of new stuff this week and this, of course, only adds to all the other stuff we have released. I got a request on one of my posts to clarify what is installed where and in what order. I’ll try to make sense of it all here.
First a couple of principles:
Now let’s look at what we’ve released.
Now let’s look at what you have to install where…
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.
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.
The Sharepoint Extensions for TFS need to be patched. There was at least one very significant performance fix.
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.
Can I create a combined RTM & SP1 installer? 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.
Do I need to uninstall the SP1 Beta before installing SP1? No, SP1 will install over top of the Beta.
Can an RTM VS work with an SP1 TFS or can an SP1 VS work with an RTM TFS? Yes to both. There is no requirement that the client and server be at the same servicing level.
If VS & TFS are on the same machine, do I need to install both VS SP1 and TFS SP1? Yes. Installing only one of them will break the other one. You must install both. The order you install them doesn’t matter but I recommend installing the TFS SP first.
Do I need to install SP1 on my TFS build machines if I upgrade my server to SP1? Yes. While not strictly necessary, we focused our testing on the scenario where the build machine and TFS server are at the same servicing level so it is the strongly recommended configuration.
What can I do if I hit an error installing one of the SPs? Often your most reliable option is to open a support case. Before that you might want to check out the VS installation forum. Also, the best blog around for staying up to date on installer issues is Heath Stewart’s. There’s also a TFS SP1 troubleshooting guide here.
Do I still need to install QFE for Microsoft Visual Studio 2010 Feature Pack 2 before I can install Feature Pack 2 now where I have installed VS SP1? No, that QFE is included in SP1
Will TFS SP1 require a reboot of our sharepoint servers? Yes, unfortunately, it probably will (when you install the SP on the Sharepoint frontends - to update the TFS extensions).
If I update my TFS and Controller infrastructure to SP1, do I have to go update all my lab agents too? No. The RTM agents will work with SP1 infrastructure but we recommend that you plan to update them at some point.
I suspect I haven’t answered all the very legitimate questions, so I’ll keep updating this post as people as more and we’ll have a nice central place you can go to find the answer.