Recommended Source Code Control Providers for LabVIEW

Updated Apr 23, 2019

Reported In


  • LabVIEW Professional

Operating System

  • Windows
  • Mac OS X
  • Linux

Issue Details

  • I want to use source code control software to manage changes to my LabVIEW code base. Which source code control providers does National Instruments recommend for LabVIEW?
  • How can I make a protected copy of my LabVIEW project that I can edit and still have that functional copy without damaging my functional copy?


Beginning with LabVIEW 8.0, the LabVIEW Professional Development System (PDS) includes integration with many third-party source control providers. This integration enables LabVIEW users to access the source control providers from within the LabVIEW development environment.
  • On Windows, the LabVIEW PDS is capable of integrating with any source control provider that supports the Microsoft Source Code Control Interface.  
  • On Mac OS X and Linux, you can use the Perforce command-line interface to perform source control operations. 
The following list includes source control providers that have been tested for integration and basic functionality with the LabVIEW PDS on Windows:
  • Perforce
  • PushOK (CVS and SVN plugins)
  • Microsoft Visual SourceSafe
  • Microsoft Team System
  • IBM Rational ClearCase
  • Serena Version Manager (PCVS)
  • PTC Integrity Lifecycle Manager (formerly MKS Source Integrity)
  • Seapine Surround SCM
  • Borland StarTeam
  • Telelogic Synergy
  • PushOK SVN
  • ionForge Evolution
  • Git

Additional Information

This list of source control providers is not intended to list all compatible providers. If a provider is not listed, that provider may or may not integrate with LabVIEW 8.x or later.  Typically, source control providers that are compatible with the Microsoft Visual Studio .NET development environment should also integrate with the LabVIEW 8.x PDS.
  • SourceOffsite was tested and proven not to be compatible with LabVIEW 8.x or later. The manufacturer does not have plans to evaluate this compatibility issue.
  • Microsoft Team System was tested with LabVIEW 8.5.
  • Currently, ionForge Evolution version 2.8 and later works with LabVIEW. Depending on the version of ionForge Evolution you use, enable IDE Integration for ionForge Evolution to show up as one of the SCC Providers in LabVIEW. To enable IDE Integration, open ionForge Evolution and select Make Evolution your default source code provider. (Enable IDE Integration) within View»Options. Close and open LabVIEW.
  • With MKS Source Integrity Client 2005, Error -2901 has been reported. The error description is Error occurred at prefPage_Source Possible reason(s): LabVIEW: An error occurred during source control provider initialization. If you experience this error, backup the Windows Registry, and then set the dllName key, located atHKEY_LOCAL_MACHINE\SOFTWARE\Mortice Kern Systems\Integrations\SCC\IDEs\National Instruments LabVIEW to use base.
  • LabVIEW by itself does not have this feature, hence we recommend the SCC software mentioned above.
  • With PTC/MKS Integrity, enable Visual Studio Integration in the PTC/MKS configuration utility that came with the source control software. If this does not work, try running the configuration utility as administrator.
For more information on source control in LabVIEW, please refer to Software Configuration Management and LabVIEW. ​