Vistual Studio 2008 正式版已經發佈，每次有新產品，最麻煩的就是和之前版本的相容性，尤其Visual Studio 至2005版開始，已經有Clirnt- Server(Foundation Server)的架構，這時相容性就更顯重要了，國外已經有位MVP Grant Holliday幫我們做了這樣的測試，請參考:http://ozgrant.com/2007/10/22/vsts-2005-2008-compatibility-matrix/
| Products |
VS 2005 |
VS 2008 |
TFS 2005 |
TFS 2008 |
Build 2005 |
Build 2008 |
TE 2005 |
TE 2008 |
Web Access |
Power Tools |
VS Addins |
| VS 2005 |
- |
Yes. Note #1 |
Yes |
Yes. Note #2, #3 |
Yes. V8.0 SLN files build. |
Yes. Note #2, #3 |
Yes |
Yes. Note #1 |
Yes |
Yes |
Yes |
| VS 2008 |
- |
- |
Yes. Note #4, #5 |
Yes |
Yes. Note #5, #6 |
Yes |
Yes. Note #1 |
Yes |
No. Note #7 |
Partial. Note #8, #9 |
Partial. Note #8 |
| TFS 2005 |
- |
- |
- |
N/A |
Yes |
No |
Yes |
Yes |
Yes |
N/A |
N/A |
| TFS 2008 |
- |
- |
- |
- |
No |
Yes |
Yes |
Yes |
Yes. Note #7 |
N/A |
N/A |
| Build 2005 |
- |
- |
- |
- |
- |
N/A |
Yes |
Yes. Note #5 |
Yes |
N/A |
N/A |
| Build 2008 |
- |
- |
- |
- |
- |
- |
Yes. Note #2, #3 |
Yes |
Yes |
N/A |
N/A |
| TE 2005 |
- |
- |
- |
- |
- |
- |
- |
Yes. Note #1 |
Yes |
Yes |
Yes |
| TE 2008 |
- |
- |
- |
- |
- |
- |
- |
- |
No. Note #7 |
Partial. Note #8, #9 |
Partial. Note #8 |
| Web Access |
- |
- |
- |
- |
- |
- |
- |
- |
- |
N/A |
N/A |
| Power Tools |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
N/A |
| VS Addins |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
Notes
| Note #1 |
You can install VS2005 and VS2008 side-by-side on the same machine. (See Aaron’s blog post below) |
| Note #2 |
For an VS2005 client to start a build on an Orcas server, the build definition needs to be stored at $/<TeamProject>/TeamBuildTypes/<name> |
| Note #3 |
VS2005 will be able to start a build, but it can’t queue a build, see the list of builds in the queue, see the list of build agents, etc. |
| Note #4 |
A VS2008 client will not be able to create a new build definition on a TFS2005 server. Workaround: You could branch an existing build type in $/<TeamProject>/TeamBuildTypes/<name> |
| Note #5 |
When starting a build, a VS2008 client will not be able to change any parameters in the dialog for a TFS2005 Server. |
| Note #6 |
A Team Build 2005 server does not understand a VS2008 Solution File. Workaround: Changing the version number inside the SLN to Version 9.0. You will also need to copy the MSBuild directory V8.0 directory to V9.0. This could be done dynamically with a MSBuild task (See workaround below) |
| Note #7 |
Team System Web Access (TSWA) relies on the TFS2005 Object Model. You must have Team Explorer 2005 installed on the server that has TSWA installed |
| Note #8 |
The current TFS Power Tools (inc. Checkin Policy Pack) are compiled against the TFS2005 Object Model. VS2008 doesn’t support loading both object models within the same process, therefore any Power Tools or addins that get loaded in VS either need to be recompiled against the TFS 2008 object model or policy needs to be used to redirect references from the TFS 2005 assemblies to the TFS 2008 assemblies. (See Ed Hintz’s blog post below) |
| Note #9 |
Non-VS add-in Power Tools (everything except the Process Template Editor, checkin policy pack and Annotate/TreeDiff) will work fine as long as the TFS 2005 Team Explorer is also installed. |