Multi-site source code control for Labview

[DeJesus]

We have an outside developer writing some labview code for us as well as in house people developing labview code. I am looking for some suggestions on a good way to coordinate source code control for both of these groups. The code written by the outside developers is often taken and modified further by the in house developers. I can get the outside developers to setup Labview's built-in SCC and I can set it up in house as well. Does anyone have suggestions on how to manage this situation? It looks to me like I will have to copy the entire SCC setup from the outside developers to my in house system periodically and clean it all up manually. Is there any way that we can use one master file location for both the outside an
d inside developers?

[Ankita A.]

Hi,

If you use LabVIEW's built-in source code control, then you can either put all the VIs on a network drive that both the outside and inside developers can access or else go by what you yourself suggested i.e.
copy the entire SCC setup from the outside developers to your in house system periodically and clean it all up manually.

Otherwise you may want to consider third pary Source Code Control systems. LabVIEW can interface with several SCC systems. You can visit the following link for more information on how you can use Perforce with LabVIEW.
http://zone.ni.com/devzone/conceptd.nsf/webmain/69EA27204D24F78586256E2400773ABE

Regards,
Ankita A.