Solution
A source code control provider must support Microsoft Source Code Control integration to work with the integrated source code control built into LabWindows™/CVI™. However, you can use any source code control provider externally without integrating into the LabWindows™/CVI™ editor. The packages that have been tested with LabWindows™/CVI™ are the following:
- Perforce
- Subversion
- Microsoft Team Foundation Server 2010
Note: Many Subversion clients are not compatible with MSSCCI. For example, TortoiseSVN is a popular Subversion client that is not compatible with MSSCCI. There are third party plug-ins that integrate Subverision MSSCCI support, such as Agent SVN; however, they are not officially tested by National Instruments.
There are two options for using an SCC package in LabWindows™/CVI™. The first is to setup your SCC at the environment level by selecting the
Options»Environment»Source Code Control menu from the Project window. This will make the SCC provider you selected the environment default for every project.
The second option is to select the SCC provider for the current project. Select
Edit»Project»Source Code Control. You can now use the
Tools»Source Code Control menu in the Project window to perform basic SCC functions such as checking files in and out.
SCC was not integrated into versions prior to 5.5 of the LabWindows™/CVI™ development environment. For more information on using SCC in LabWindows™/CVI™ see the Users Manual that ships with LabWindows/CVI.
Note: The list of SCC providers is
not intended to list all compatible providers. If a certain provider is not listed, it may or may not integrate with the LabWindows™/CVI™ development environment.