NI-lesson or tutorial about Project and Versioning

[MAILFERTSeb]

Dear community,

I'm looking for a NI-lesson or tutorial about projects (how to create, duplicate, best practices, etc.) and about versioning (how is it done in Labview, best practices, etc.).

Do you have links where I can learn how to optimize and work safely with projects and versions of Vis?

Thanks for your answer.

[GerdW]

Hi CIML,

---

@MAILFERTSeb wrote:

I'm looking for a NI-lesson or tutorial about projects (how to create, duplicate, best practices, etc.)

---

Basic learning is provided in the "Training resources" at the top of the LabVIEW board.

Those lessons should show how to create a (LabVIEW) project.

Duplicating a project can be achieved by using the options in the save process…

---

@MAILFERTSeb wrote:

about versioning (how is it done in Labview, best practices, etc.).

---

Setup your preferred SCC (source code control) tool. I use SVN, many use GIT, some use other SCC tools out there…

Read the manual for that SCC tool to learn about its options and usage.

LabVIEW offers SCC integration in its options, but I never used that so far.

There are also toolkits available in VIPM offering assistance for SCC.

Best practice: enable "separate compiled code" in the LabVIEW (or project) options to easy the SCC process!

[billko]

---

@GerdW wrote:

Hi CIML,

---

@MAILFERTSeb wrote:

I'm looking for a NI-lesson or tutorial about projects (how to create, duplicate, best practices, etc.)

---

Basic learning is provided in the "Training resources" at the top of the LabVIEW board.

Those lessons should show how to create a (LabVIEW) project.

Duplicating a project can be achieved by using the options in the save process…

---

@MAILFERTSeb wrote:

about versioning (how is it done in Labview, best practices, etc.).

---

Setup your preferred SCC (source code control) tool. I use SVN, many use GIT, some use other SCC tools out there…

Read the manual for that SCC tool to learn about its options and usage.

LabVIEW offers SCC integration in its options, but I never used that so far.

There are also toolkits available in VIPM offering assistance for SCC.

Best practice: enable "separate compiled code" in the LabVIEW (or project) options to easy the SCC process!

---

The other day I learned a practical lesson on GIT vs SVN for LabVIEW.  GIT is very expensive disk-wise because you have a complete repository everywhere you go, and since LabVIEW VIs are binary, and (if done properly) there are lots of them, the disk space is eaten up very quickly, whereas with SVN, this only happens once, on the disk where the one repository resides.  However, GIT is very convenient in that, because they are complete repositories, you can work offline and commit your work, updating when you get back online.

[MAILFERTSeb]

Thanks for your answers.

The Lesson Labview CORE 3 explains project management

[AeroSoul]

I use GIT, with Sourcetree as the "visual" interface, since there exists a Sourcetree custom diff tool for labview files.

[billko]

---

@AeroSoul wrote:

I use GIT, with Sourcetree as the "visual" interface, since there exists a Sourcetree custom diff tool for labview files.

---

I use TortoiseGIT because I use TortoiseSVN and the interface is something I am very familiar with.

[BertMcMahan]

I also use SVN with TortoiseSVN and like it. I do NOT have it integrated in LabVIEW though and just use it in Windows Explorer. I had it tied into LV for a while but it caused some crashes and I didn't find it added anything better than TortoiseSVN did in Windows Explorer.

My company is considering switching to locally-hosted Git though due to the ability to do commits outside of the network, as well as the managed pull requests, etc. I don't think SVN offers that natively, though there may be a way to implement it with some custom scripting and user accounts. It just seemed to be more "baked in" to Git.

Either way.... DEFINITELY use SCC! There are lots of good historical threads discussing various facets of SCC on the boards if you do some searching.