|LabVIEW 2015 Help|
|LabVIEW 2016 Help|
|LabVIEW 2017 Help|
|LabVIEW 2018 Help|
|LabVIEW 2019 Help|
LabVIEW supports several third-party source control providers. Available source control operations in LabVIEW are the same regardless of which third-party provider you select. Specific support or functionality for each operation varies by provider. For example, you cannot create Perforce configuration files in LabVIEW.
In some cases, you might decide to use a specific source control provider because your company has standardized on that application. If not, you must decide which provider you want to use for managing your files. Consult the source control administrator at your company to find out if you should use a specific provider.
After you select and install a source control provider, you must configure LabVIEW to work with that provider. You can configure LabVIEW to work with only one source control provider at a time.
LabVIEW includes two source control integration interface types. On Windows, LabVIEW integrates with any source control provider that supports the Microsoft Source Code Control Interface. On non-Windows platforms, LabVIEW integrates with Perforce using a command line interface.
From all of the following third-party providers tested with LabVIEW, National Instruments recommends using Perforce or SVN when working with source code control.
|Note The LabVIEW Perforce Command Line offers additional source control functionality such as VI compare.|
|Note Currently, ionForge Evolution version 2.8 and greater works with LabVIEW.|
Refer to the support document at ni.com for the most current list of third-party source control providers that work with LabVIEW.
Refer to the Software Configuration Management and LabVIEW article at ni.com for more information on source code control integration with LabVIEW.