Include Source Code Control in LabVIEW Developer Suite

[JackDunaway]

As part of the base package in the LabVIEW Developer Suite, include an integrated SCC in the IDE. We are using a third party SCC program right now, and it has it's quirks when integrating with LabVIEW. Our group is comfortable with the quirks now, but for a new group starting a new project, the hurdles might be big enough to nix SCC. If a LabVIEW-specific package was maintained with the IDE, those quirks could be reconciled for the LabVIEW-specific style (i.e., a file is "modified" when compiled, diffing two VI's, ...)

NI has been really promoting SCC recently, and I think they should officially develop (or adopt) an integrated package with the LabVIEW IDE.

[Dennis_Knutson]

LabVIEW used to include it's own SCC system. I've only used Source Safe and SVN and the NI tool wasn't nearly as good. I'd much rather NI spent the time and effort on LabVIEW instead of duplicating code that already exists.

I believe that NI uses Perforce internally. If they were to adopt that as a standard, would you want to pay the additional license fee? 

[JackDunaway]

I have also heard rumors that NI also uses Subversion internally. (Can anyone confirm this?) The price of this software package is much more reasonable! 

[Ian_Phillips]

I'm just about to try TortoiseSVN with the JKI framework (http://blog.jkisoft.com/category/products/tortoisesvn/).

[Matthew_Kelton]

At NI Week several years ago, their was a session about SCC.  The moderator asked the room (it was packed) if anyone used the LabVIEW SCC tool.  No one raised their hand.  As Dennis said, I think NI saw it wasn't worth the man hours they were putting into it and most mid-large companies have their own system.

There are also several free alternatives out there if you can't afford the "good" ones.  I used the NI one for one project because we had an outside controactor working on the project and the company I was working with at the time didn't have anything in place and wasn't about to spend any money on it.  It was able to do the job, but it was not an ideal choice.

[ClaudioH]

Hi,

We used LabVIEW 6i to 7.1 SCC built-in and we miss it in 8.0.

After we adopted CVS and SVN with Tortoise to manage SCC.

I would like to see LabVIEW recognize a server or directory handled by CVS and SVN or let us to set when configuring LabVIEW 2011.

Today we need to go to Win Explorer, do check in or check-out and return to LabVIEW 2010.

Cheers