LabVIEW Source Control

[RyanN]

I'm still new to source control, and the other threads I've seen haven't been helpful so far.

Team Fusion is setup in a classroom at Gulfport High School. We're not allowed to connect our computers to the school's network, so that also means no internet (bye bye github, bitbucket, and all the other great repositories). I'd like to implement some time of source or revision control for our code. We would have to setup a PC with some type of subversion server.

At NASA, we used TortoiseSVN on top of Windows to hold our code. That's possible, but it doesn't integrate with LabVIEW very well. I'd like to be able to compare, merge, and do all of the other normal source control system functions (push, pull, merge, commit) with LabVIEW files.

So the question is, what does your team do?

[bvisness]

Our (very unprofessional) way is just to duplicate the project folder and rename it whenever we are about to make a significant revision to the code. Last year we ended up at Competition Code v5.lvproj.

[Greg McKaskle]

This blog seems pretty full on info.

http://forums.ni.com/t5/LabVIEW/LabV...t/true#M607335

Greg McKaskle

[DominickC]

This year our team's programming mentor suggested setting up some sort of version control system, so we went with SVN.

TortoiseSVN is our preferred client. It preforms all of the functions you said it doesn't (merge, visual diff, push, commit, update). The people who head the Tortoise project also have an SVN monitor tool to alert you to new commits by polling the SVN server every x number of minutes.

Tortoise's integration with LabVIEW was nearly plug-and-play. The only thing that required a little bit of effort was selecting the visual differencing VI from the correct directory.

Dom

[Mike AA]

Or, since nearly everyone now adays has a smart phone turn on someones tether mode or wifi hotspot and link the computers to the internet that way.