| 42 ratings: |
|
3.35 out of 5 |
Which Third-Party Source Control Providers Can I Use with LabVIEW 8.0 and later?
Primary Software: LabVIEW Development Systems>>Professional Development System
Primary Software Version: N/A
Primary Software Fixed Version: N/A
Secondary Software: N/A
Problem: I would like to use source control software to manage changes to my LabVIEW code. Which source control providers have been tested with LabVIEW 8.
x?
Solution: 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 8.
x PDS is capable of integrating with any source control provider that supports the Microsoft Source Code Control Interface. Typically, source control providers that are compatible with the Microsoft Visual Studio .NET development environment should also integrate with the LabVIEW 8.
x PDS. 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 8.
x PDS on Windows:
- Microsoft Visual SourceSafe
- Microsoft Team System
- Perforce
- Rational ClearCase
- PCVS (Serena) Version Manager
- MKS Source Integrity
- PushOK CVS
- PushOK SVN
- Seapine Surround SCM
- Borland StarTeam
- Telelogic Synergy
- ionForge Evolution
This list of source control providers is
not intended to list all compatible providers. If a certain provider is not listed, it may or may not integrate with the LabVIEW 8.
x PDS. If a source control provider is compatible with the Microsoft Visual Studio .NET development environment, the source control provider should integrate with the LabVIEW 8.
x PDS. Please refer to the link below for information about how to access third-party source control providers from within the LabVIEW environment.
Notes:
- SourceOffsite was tested and proven not to be compatible with the LabVIEW 8.x PDS. 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 greater works with LabVIEW. Depending on the version of ionForge Evolution that is being used, you will want to enable IDE Integration for ionForge Evolution to show up as one of the SCC Providers in LabVIEW. To do that, 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 Control.vi Possible reason(s): LabVIEW: An error occurred during source control provider initialization. If you experience this error, you should backup the Windows Registry, and then set the dllName key, located at HKEY_LOCAL_MACHINE\SOFTWARE\Mortice Kern Systems\Integrations\SCC\IDEs\National Instruments LabVIEW to "use base".
- With MKS Source Integrity, it is necessary to enable Visual Studio Integration in the MKS configuration utility that came with the source control software.
Related Links: NI Community: Source Code Control and Group Development Practices in LabVIEW for Advanced Configuration Management Tasks
Attachments:
Report Date: 08/31/2005
Last Updated: 10/16/2008
Document ID: 3OUF5N1Q
