A couple of weeks ago I posted the way to connect Visual Studio 2008 to Team Foundation Server 2010, 2012 and the Team foundation Service. Back then, there was a similar way to connect Visual Studio 2005 to Team Foundation Server 2010, but not yet to the latest 2012 version and the Service. The word was that it was underway, but in the end it never made the cut.
3 Oct 2012 11:59 AM
We ended up deciding not to do the same kind of compatibility update for VS 2005. We released compatibility updates for VS 2010 and VS 2008 (and, of course VS 2012 works). Versions before VS 2005 have always been supported via a MSSCCI provider for version control integration and side-by-side Team Explorer for other capabilities. We've decided to take that approach for VS 2005 now as well. So we updated the MSSCCI provider to support TFS 2012 and added support to make it work with VS 2005. Other capabilities can be accessed in a side by side fashion with a newer Team Explorer (which is a free download).
Brian
There is a way to solve this, but it's a lot more involved than with the 2008 version and doesn't work on Windows XP, due to the requirement of having Team Explorer 2012 installed (which in turn requires .NET Framework 4.5). For those still on XP, you'll have to be a little patient, Microsoft is working on fixing the MSSCCI 2010 provider. When that becomes available I'll update this post.
It’s also worth noting that we are planning to expand support for MSSCCI 2010 to enable VS2005 clients to work against TFS2012. Some customers are currently using a side-by-side workaround since they have VS2005 on XP and can’t use MSSCCI 2010 with VS2005 (it blocks) and can’t use MSSCCI 2012 because it doesn’t support XP.
First download the following things:
Then install them in that order.
Next, open up Visual Studio 2005 and go into the Tools, Options and find Source Control. Select the MSSCCI provider.
Now you can connect to TFS 2012 through the old Source Safe interface. You won't get integration with Work Items, builds or other features; just Source Control. Remember, just as with Visual Studio 2008, you need to use a different TFS url to connect.
Instead of 'https://[server]/tfs' use 'https://[server]/tfs/[projectcollection]'. To connect to the TFSvc, use 'https://[youraccount].visualstudio.com/DefaultCollection'.
If you want to access any of the other features, you'll need to fire up Team Explorer 2012.
It's the best you can get. Since you won't be connecting Visual Studio 2005 directly to TFS anymore, there's no dependency on the installation order for Business Intelligence Development Studio 2005 (BIDS) or any other product that integrates into Visual Studio 2005.
