LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Best source code control program

What is the best source code control to use with Labview. I have
looked into the built in SCC in 5.1.1 and it lacked big time. NI
suggested Visual Soure Safe. Has anyone used VSS with Labview?

Thanks

John Wilson
Ford Motor Co.
0 Kudos
Message 1 of 7
(3,784 Views)
It works fine. The only problem is when you have multiple projects with shared VIs. You have to do the labeling manually otherwise you will not be able to get a labeled version with only those VIs that belong to the specific project. (You will get all of them).

Regards,

Andras Ferencz
0 Kudos
Message 2 of 7
(3,784 Views)
john wrote in message
news:3a904cb1.11162792@news.chi.ameritech.net...
> What is the best source code control to use with Labview. I have
> looked into the built in SCC in 5.1.1 and it lacked big time. NI
> suggested Visual Soure Safe. Has anyone used VSS with Labview?
>
> Thanks
>
> John Wilson
> Ford Motor Co.
Sourcesafe is good. Sourcesafe looks like an explorer window. A Labview
application is no different from any other as far as sourcesafe is
concerned.
0 Kudos
Message 3 of 7
(3,784 Views)
rlw2@hotmail.com (john) wrote:

> What is the best source code control to use with Labview. I have
> looked into the built in SCC in 5.1.1 and it lacked big time. NI
> suggested Visual Soure Safe. Has anyone used VSS with Labview?

Look into Perforce. Some of the developers at a company in Austin use
it, and it seems more flexible than the MS product. We've found it
better for our needs than the other systems. It has a web client (any
platform), and the server can run on any UNIX or NT platform.

http://www.perforce.com

For single person projects, I still prefer making sit or zip archives
and storing them on a server.

- andrew johnson
- Wireworks West
0 Kudos
Message 4 of 7
(3,784 Views)
Andrew,
I downloaded the free version but Labview does not seem to see it (It only gives "build-in" as an option for SCC systems under Administration). Could you provide a little bit more specific info on setting up Perforce?
zwang@npphotonics.com
0 Kudos
Message 6 of 7
(3,784 Views)
We use ClearCase. Its cross platform compatible between UNIX and
Windows. When using it in Windows it operates just like explorer adding
a few menu choices. It is pretty easy to use, kind of steep on the
Admin side though. My only experience is using it with large
development projects with lots of users. For that its good.

For small projects I just use winzip. I found a freeware somewhere that
automatically makes archives using as scheduler. Something to think
about.

Jim

john wrote:

> What is the best source code control to use with Labview. I have
> looked into the built in SCC in 5.1.1 and it lacked big time. NI
> suggested Visual Soure Safe. Has anyone used VSS with Labview?
>
> Thanks
>
> John Wilson
> Ford Motor Co.
0 Kudos
Message 5 of 7
(3,781 Views)
John,

I would recommend evaluation of Perforce, Visual Safe Source, and perhaps a couple of others (including National Instrument's own version.)

My company uses Visual Safe Source. As manager of LabVIEW programmers, I am unhappy with VSS. I tend to want software that is as easy to use as LabVIEW is. VSS is about as easy to use as programming in Microsoft Visual C++. However, that analogy goes farther than you would imagine.

While not an easy interface, I have had mostly good results with VSS. It appears that when you know all the workarounds and bugs, that it is quite a great product. However; given that I have to be concerned with interface and ease-of-use, I tend to really despise VSS. First of all, it is set in Windows 3.1 paradigm. Why the interfa
ce isn't any better than it is questionable, of course, I have my opinion (Microsoft's core business isn't software, it is making profits. And profits don't come from GOOD products, only USEABLE products.....but that's my opinion).

Having reviewed PerForce, I tend to like this product. First of all, the interface appears to be much more intuitive. However; I haven't used it. Perhaps someone else can compare Perforce and VSS's interfaces. Most important to me is that Perforce has multiple platform and even simultaneous multiple platform implementation. In a world that is quickly waking up to the fact that Microsoft isn't the solution to everything, having a portable or interplatform product is important. You may find that your developers are on diverse platforms (Please tell us otherwise...) and would prefer an independent or interplatform method.

It's basically a matter of implementation.

For LabVIEW programmers, try to look into alternatives to VSS. LabVIEW programmer
s are generally not accustomed to interfaces such as VSS. I also hear that the LabVIEW interface to VSS is prone to problems, but I cannot confirm this.

Basically, look around. Evaluate. And Good luck.
0 Kudos
Message 7 of 7
(3,781 Views)