Source Code Control

[Jim from DME]

I have the task of trying to get a fairly large group of labview vi's and support files under source code control. I'm trying to do this using the internal SCC that comes with the profesional version of Labview 6.1. Without citing specific problems, the task has been a bit frustrating and, so far at least, unsuccessful. I'd be interested in hearing opinions from others that have used the built in SCC. Are there better ways of getting vi's under source control or should I stick with the built in SCC?

[Evan]

Jim,

Here is my short and sweet answer for you.

Use a professional Source Control Package such as Perforce or SourceSafe. The built in SCC is not real robust for large applications or a large amount of users. In the end NI's strengths are in the programming language itself not in SCC. One nice thing is that you can use Perforce with NI's SCC. So you can congifure the LabVIEW SCC to check things out from Perforce, which can be useful.

[Philip_Courtois]

Take a look at the tutorial �Using Source Code Control with LabVIEW and Perforce� to get an idea of how to use Perforce with LabVIEW 7.0.

Best regards,
Philip C.
Applications Engineer
National Instruments
www.ni.com/ask