There is no dependency between the TFS and VS service pack (confirmed by MSFT).
There is however a dependency between the .NET Framework 3.5 SP1 and VS2008,
because there are in the service pack new features that are not supporeted in
the .NET framework 3.5 RTM.
- Ewald
From: [EMAIL
Jonathan,
A custom webpart should be registered as a safe control
before it is deployed. You can find the registered webparts in the
SafeControls of the web.config section. This is typically in $drive
\inetpub\wwwroot\wss\portnumber directory. (If you can't find a
portnumber
Deepak,
Thank you for the quick response.
We don't have any custom webparts; our SharePoint portal has no
customizations at all.
I checked the web.config and these are the SafeControls:
***
SafeControls
SafeControl Assembly=System.Web, Version=1.0.5000.0, Culture=neutral,
There is a dependency.
Bits from the install guide TFSInstall-SP1RTM-v080812.chm (section:
Installing Team Foundation Server and Service Pack 1)
http://www.microsoft.com/downloads/details.aspx?FamilyID=ff12844f-398c-4
fe9-8b0d-9e84181d9923displaylang=en
You must install SP1 in the
I am currently in what appears to be exactly the same situation as
Jonathan was.
I just upgraded a TFS Server from 2005 to 2008 on new hardware after
performing a restoration based move. The move went fine and SharePoint
was working as expected.
Becasue it was a new TFS 2008 installation I
Is there guidance for an integrated installation onto a clean server if
you were planning to have both the client and server components on it.
What would the install order be:
1. Integrated TFS 2008 SP1
2. Team Explorer 2008
3. VS 2008 SP1
Or
1. Team Explorer 2008
2. VS 2008 SP1
3.
