Source Code Control in CVI - Any changes?

[tstanley]

Are there any plans to change how the source code control is handled in CVI?  From my understanding, CVI interfaces through the "MSSCCI" interface, which is from Microsoft's Visual Source Safe system.  It seems that Microsoft is depreciating this interface - Visual Source Safe is discontinued, and the replacement for VSS is Team Foundation Server, which uses the newer, "VSIP" interface and only offers the MSSCCI interface through a plugin (link).  Is there any plans to have CVI support this newer interface, or perhaps some other interface (like for Subversion), or is CVI sticking with the MSSCCI interface for now?

I guess as a more general question, does anyone have any experience using CVI with Team Foundation Server using the MSSCCI plugin?

Thanks.

[Shelby S]

Hi,

As far as moving towards the newer VSIP, that is currently unknown.  Currently CVI source control has been tested to work with Visual Source Safe, Perforce, ClearCase, and PVCS.  Although the SCC/MSSCC is older, the API is still very much in use across several source control programs.  With regard to the plugin, that isn't somthing that I have experience with, so I'm not sure how it will integrate with our software.  Unfortunately we don't have the licenses to use Team Foundation Server from Microsoft, so it's difficult to give a concrete answer.

[tstanley]

Thanks for the information.  We're looking into different solutions at the moment, just wanted to know if there were any changes planned before we commit to something.