Source Code Control FAQ?

[Mareike]

Hi,

I'm looking for a "How to"-document for the Source Code Control.
What kind of experience do you made with SCC? Is SCC practicable for
professional use? What is the advantage over MS Visual SourceSafe?

Mareike

[Labviewguru]

Marieke,

My company uses Visual Source Safe. For the price (Free with MSDN) it is well worth the money (get it?)

VSS does an adequate job, but is sometimes unreliable (get latest version doesn't always do that, for example) and the user interface is antiquated (Windows 3.x API!) and is extremely difficult to use, and often counter-intuitive. However, given the results, it is certainly better than nothing.

NI uses Perforce. I have not seen it, but I have seen a lot of good features of it, and hear a lot of good things. It is very expensive, but is highly recommended.

Oh, one last thing. LabVIEW has native SCC. Try it out. You may find this adequate, and it's included in the PDS.

Good luck.

[Mareike]

Thank you!

Mareike

[Matt_K]

There are a couple of good sources for further information on Source Code Control. One reference is Chapter 11 of the Professional G Developers Tools Reference Manual. You can access the Manual from the following link: http://digital.ni.com/manuals.nsf/webAdvsearch/57CC60D27B73A6FB8625665E00635940?OpenDocument

Also, there is documentation included in the Labview help. Just go the Labview help menu then select 'contents and index'. In the help topics, select 'Labview Professional Tools' and then 'Source Code Control Tools'.

Also, here's a couple advantages I came up with:
1) Source Code Control is already integrated into the Labview Professional Development System.
2) You can access vi's from multiple platforms. I have a feeling you wouldn't be able to
do this with Microsoft's version.

Matt Kisler
Applications Engineer
National Instruments
http://www.ni.com/ask