I was at a client yesterday, who wanted to migrate from Source Safe and a lot of other tools, to Team Foundation Server. Problem was, they stil had some older VB6/ASP projects, and of course a lot of .NET 1.1 projects. For a lot of reasons, these cannot always just be upgraded to .NET 2.0. Conversion will take time, testing even longer, even though it seems everything works out great.

They had come up with all kinds of solutions to start using TFS Source Control for their older projects, like using just the Team Explorer besides VS2003 & VS6. Or start using .NET1.1 templates for VS2005.

A much more clean and simple solution however is, to use the "Team Foundation Server Microsoft Source Code Control Interface", or TFS MSSCCI. It has ‘just’ been released and supports at least the following IDE’s:

  • Visual Studio 2003
  • Visual Basic 6 SP6
  • Visual C++ SP6
  • Visual FoxPro 9 SP1
  • Microsoft Access 2003 SP2
  • SQL Server Management Studio 2005

As usual, unsupported and provided "as is", blah blah blah… The usual Microsoft customer care… But you’re allowed to ask questions on their forums. 😉

You may also like...

2 Responses

  1. Chi Wai Man says:

    Cool i will give it a try. I just installed tfs rtm just a few weeks ago. To bad they don’t support interdev.

  2. MSSCCI is some kind of protocol, or whatever it’s called. Multiple IDE’s use it. Every IDE that uses it, should be able to connect to TFS Source Control now. So who knows Interdev will also support it. Perhaps Microsoft haven’t tested it yet, because of lack of support these days, or something.

Leave a Reply

Your email address will not be published. Required fields are marked *