LabVIEW Version Control

[s5511]

Our team is going to be using LabVIEW for the next season, and we were wondering how you all do versioning control for your code. We are currently using GitHub, but it does not allow commit and push code well since we cannot see the visual VIs that are being changed.

[Greg McKaskle]

If you haven't already done it, you might want to do a web search for LabVIEW and GIT and read through some of the tutorials and instructions. Some are from industrial users and some from teams and from NI.

Internally, we use Perforce and less distributed SCC tools, so I don't have any GIT specific experience to share.

The basic concept is to configure GIT so that it knows to use LVCompare and similar tools to be able to deal with different version of the file.

Greg McKaskle

[sraque]

Similar to what Greg suggested in his post, the same can be done using SVN for version control. Both GIT and SVN will do the job for you. The decision will be dependent on which tool some of your members have experienced or have access to. For example, one of our sponsors provides us space on Unfuddle, so we use it and its SVN integration.