Installer CRASHES. Each time it does this I need to reboot.
Eventually just delete the SQL Server version check from hcpackages.xml
It looks like it’s installing now.
16 hours later. TFS Server 2005 took me merely 4-5 hours (did it twice). Considering it’s a test-bed server where I am going to continue working on integrating K2 with TFS Server (we are going to be using K2 to automate our builds) this was just plain ridiculous.
It’s clever, and that’s about it, to use Sharepoint. It seems as though TFS might have started off as a Sharepoint extensibility test. Things would be far easier were it not for the whole Sharepoint dependency (and analysis and reporting – I don’t need this).
These guys need to take a hint from the ASP.net team.
Jonathan Dickinson works at SourceCode. Everything posted on this blog is his personal opinion and do not necessarily represent the views of his employer or his employer's clients.
TFS Server 2008 – Fail
It’s an amazing server. The installer needs A LOT of work. Here is what happened to me:
16 hours later. TFS Server 2005 took me merely 4-5 hours (did it twice). Considering it’s a test-bed server where I am going to continue working on integrating K2 with TFS Server (we are going to be using K2 to automate our builds) this was just plain ridiculous.
It’s clever, and that’s about it, to use Sharepoint. It seems as though TFS might have started off as a Sharepoint extensibility test. Things would be far easier were it not for the whole Sharepoint dependency (and analysis and reporting – I don’t need this).
These guys need to take a hint from the ASP.net team.