Submit My Question - Recent Questions - Recent Answer
Msdn Tech >> Visual Studio Team System >> Team Foundation Server - Version Control

MSSCCI provider causes VC6 crash

After installing the MSSCCI provider, launching VC6 by double-clicking the Xxxx.dsw file now causes VC6 to crash at startup.When I launch VC6 alone and open this same Xxxx.dsw file (through Open Workspace…), it gives me the error "Illegal characters in path."I get this error after selecting the correct TFS server and folder location for the project.

What steps must one go through to take a VC6 project and get it to use TFS for source code control?Is there any documentation for how to transition to using the MSSCCI provider?I have already converted the old SourceSafe database over to TFS-VC, just not sure how to make the VC6 project happy with the new location.

Is anyone else having this problem?

Incidentally, uninstalling the MSSCCI provider does get rid of the crash on startup, but naturally takes me back to my SourceSafe database.

[1501 byte] By [Dave_Novak] at [2008-2-11]
«« Property displaying lists
»» Changing ports sql 2005 listens on.
# 1

In terms of steps one must go through to take a VC6 project and get it to use TFS for source code control, I got the following to work:

  1. Convert VSS database to TFS-VC database. See http://blogs.msdn.com/akashmaheshwari/articles/474256.aspx for details. Also, the VSS Converter GUI is worth a look (http://www.epocalipse.com/blog/2006/04/06/vssconverter-gui).
  2. From Team Explorer, check out the VC6 workspace and its projects.
  3. Manually edit the project files, updating settings for # PROP Scc_ProjName and # PROP Scc_LocalPath to point to your TFS-VC database and local workspace, respectively. Also, for xxxxx, get rid of that trailing , JGFAAAAA" [or some garbled name], which is an obsolete reference to the SourceSafe file.
  4. To load the workspace in VC6, first start VC6 and then go to File à Open Workspace… Launching the .dsw file will cause VC6 to crash with the TFS MSSCCI provider installed. Everything should now behave normally, except that you will be using TFS instead of VSS.

I hope this helps.

If there's a better way of doing this, please let me know.

Dave_Novak at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - Version Control...
# 2

Unfortunately, there is no UI mechanism provided in VC6 to unbind and rebind a solution or project to SCC. Therefore, you have to resort to manual steps. The instructions you provided are probably the best solution for this issue.

The only alternative I can think of would be to bypass doing the VSS to TFS conversion, manually strip the SCC binding information from the project files and then bring the projects up in VC6 and add them to TFS source control.

--Ben

BenRyan at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - Version Control...
Visual Studio Team System
Team Foundation Server - Version Control

Visual Studio Team System Hot Topic

Visual Studio Team System New Topic

Visual Studio Team System

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech

Site Classified