Versioning

[Jonas_Stein]

When i write code i use git to save versions, see differences and get back to an old version if necessary.

What is the best way to save development steps in LabView?

[Dippi]

Hi asdfsfdasdafasdf,

the best way to do this is to use "Source Code Control" software like Perforce, TortoiseSVN (Subversion),...

TortoiseSVN is e.g. freeware and therefore most of our customers are using TortoiseSVN.

Here you can learn how to use TortoiseSVN.

Hope that help

Best regards

Dippi

[GuenterMueller]

Stay with git.

It's distributed approach is much better than SVN.

Guenter

[Jonas_Stein]

Ok. I thought there would be something special for LV Projects. I think svn would be even worse than git.

By the way there is a tortoise-clone for git too, if someone found this thread some day.

Is there a tool, that can show differences for example as picture in the blockdiagram?

[GuenterMueller]

LabVIEW is able to compare VIs.  If you use TortoiseGit, you just have to specify LabVIEW.EXE as the "Diff Viewer" for VIs.
Guenter

[Jonas_Stein]

that sounds interesting. I will try that. Thanks a lot.

[Matthew_Kelton]

You can read my blog series on the subject.  This thread has all the links to the blog entries.

You won't find any of the free VCS's plugging into LabVIEW.  JKI has a toolkit for svn, which will give you some integration, but I would gladly give up integration for LabVIEW for the distributed system.

If you have the Professional version of LabVIEW, there is some SCC integration, but it supports a very specific standard, which none of the open source VCS's approach.  The Mercurial User Group is working on creating one for Hg.

Also, if you want to diff and merge VIs, you also need the Professional version of LabVIEW and use the LVMerge and LVCompare tools.  There currently is no support that I am aware of for projects, classes, and lvlib merging or diffing.  These are all text based files, so you can look at them to get an idea of what the changes are.  You probably don't want to try to edit them in a text editor, though.

[SnowMule]

We use Perforce here and it works well.  Pretty easy to use and it integrates well with LV.

[JÞB]

---

@SnowMule wrote:

We use Perforce here and it works well.  Pretty easy to use and it integrates well with LV.

---

Thats because..... NI uses Perforce! 

[Jonas_Stein]

i just tried perforce. There is a no cost version of it with some limitation. (<4 Users)

LV found Perforce as VCS, but when i try to add files i get the attached Error

I hope NI will support git soon. Its much better then perforce.