Using Source Code Control

Complete the following steps to configure and use the built-in SCC system.

  1. Administrator sets up system—Each source code control provider has a different procedure for configuring its system. If you are using LabVIEW's built-in system, there is an option during installation to be an administrator. Refer to your provider's documentation or contact your administrator for more information.
  2. Users configure the SCC system to access the system—The main decision users must make is where to place their local work directory. The local work directory is a directory on the local system where all VI development takes place. As you retrieve files from SCC, the SCC system places them inside this directory and its subdirectories. You cannot add files to SCC that are outside of this directory.
  3. Users set up VIs for use with the SCC system—As mentioned above, all files that users will work with must be in the working directory or in one of its subdirectories. In addition, files that you store under LabVIEW's built-in SCC system cannot be stored in LLBs. LLBs are not flexible enough to work well with the built-in SCC system because they do not allow for easy access to individual files. To convert LLBs to directories of VIs, select Tools»VI Library Manager to display the VI Library Manager dialog box. When using a third-party SCC provider, you have the option to leave VIs in LLBs. However, all source code control operations on a VI are performed on the LLB containing that VI, not on the VI itself.
  4. Users use SCC commands to access project files—At this point, you can begin to work with files under SCC. All commands related to SCC are in the Tools»Source Code Control menu. Following is a brief description of the commands: