Please give us access to Subversion integration in cheaper versions of LabVIEW

[ToeCutter]

A version control system is a must these days, but rearranging project files in LabVIEW is a nightmare without integrated support.

The correct way to do things is in LabVIEW rather than the file manager to save creating headaches and conflicts in LabVIEW.

The correct way to do things to maintain subversion history and minimise headaches related to subversion is in the file manager using subversion tools (e.g. TortoiseSVN).

So without subversion integration, we are damned either way.

Please provide a way we can get this support without doubling the cost of all our licenses by upgrading to Professional for this one feature (management will never go for it) . Please consider adding it to cheaper versions, or at least make it available as an optional addon for a reasonable price.

[crossrulz]

You really need to look into Viewpoint's TSVN Toolkit for LabVIEW.  It is FREE.

http://www.viewpointusa.com/product/ni-labview-toolkits/tsvn-toolkit/

Also available through the LabVIEW Tools Network.

[TiTou]

the thing is that now lots of people are dropping SVN fot Git or Hg or other SCC (see this SCC comparison) so putting effort into supporting only SVN might not be the best of ideas.

on it's way to becoming a general purpose programming language, LabVIEW needs to provide ways for developper to integrate any SCC.

ViewPoint integrated SVN quite well so now the way is open.

[ToeCutter]

Thanks for the comments, guys; I will certainly take a look at TSVN toolkit!

I would still like to see official support in cheaper versions of LabVIEW, however. To address your point, TiTou, whilst I agree with your comments, NI already provides SVN support in their professional suite so this idea is related purely to their licensing policy and wouldn't require much if any technical resource to provide.

I really think version control support is so fundamental these days that it should be available even in the base version. Just my two cents.

[Intaris]

Does the professional suite really have built-in SVN support?  I've never noticed.  We use TortoiseSVN external to LabVIEW.

Is this a new addition or something?

[ToeCutter]

Sorry Intaris, I may have unintentionally mislead.

Looking at...

https://www.ni.com/en/shop/labview/select-edition.html

...under 'programming environment' it states 'all functionality' next to 'source code control' against the professional edition. I saw that and in my mind it meant 'Subversion integration'. Perhaps someone with a pro license can confirm or deny what functionality this encompasses?

[crossrulz]

No, LabVIEW does not have built-in support for SVN.  It does have support for some SCC software.  It  supports the Microsoft Source Code Control Interface.

Selecting a Source Control Provider (LabVIEW Help)

Ok, that link shows PushOK has an SVN plugin that works.

But do notice that the source control support in only for the Professional version of LabVIEW.

[ToeCutter]

Thanks- in light of that info this idea is pretty much 'null and void' - well as far as subversion goes at least.

I am surprised at the choice of supported providers. I would imagine SVN is vastly more popular than many on the list.

[crossrulz]

Remember that LabVIEW has been around for a very long time.  SVN is fairly new in comparison to those other tools.  I am willing to bet that NI put that functionality in for them to use Perforce and it has barely been touched since.

[Intaris]

I used perforce for a while but to be honest, I prefer doing my manipulation of the SCC files outside the project environment.

[AristosQueue (NI)]

Crossrulz: "That functionality" is supported by many SCC systems... my understanding (and here I'm passing on second hand information that may be incorrect and subject to revision if someone with more direct information posts later) is that LabVIEW uses an API that the various SCC vendors all agreed on to allow tools like LV to talk to many different systems through a common DLL interface. The problem with that approach -- obviously -- is that it provides only support for those features that are common to all the SCC tools. Supporting any given SCC system has proven tricky for us because they do have radically different approaches to file management and change tracking. My understanding is that deep support for any given SCC system pretty much has to be something that is built on a case-by-case basis, and for that reason, tools from third parties like Viewpoint are exactly what we would encourage rather than splitting NI's focus from LabVIEW itself onto individual SCC tools. But obviously we cannot rely on third parties across the board, so we have to have some integrated functionality. Improving SCC integration is one area where there is considerable R&D effort. I do not know the details of what particulars we are looking at (and if I did know I wouldn't comment directly on future functionality), but threads like this one do get seen by the developers working on LV's SCC support.