LabView project refactoring strategy

[michele.santucci]

Hallo,

I'm pretty new to LabView (I had some experience with CVI in the past years and a quite big experience in standard coding) but now I have been tasked into refactoring a pretty big project composed mainly by subVIs distributed over several folders/subfolders.

I have been asked to:

1) migrate from a source distributed solution to a compiled application;

2) merge subVIs into packed libraries (where possibile);

3) create setup to distribute the application.

I created the project (it was missing) and started creating the main executable and it seems to work right now.

I would like to go on and merge VIs into Packed Libraries but I have a doubt:

bindings between subVIs merged into Packed Libraries will survive the procedure or I will need to replace every reference?

I'm working on LabView 2013 SP1.

[Jacobson · Accepted solution]

In order to create a packed library you first have to create a LabVIEW library (.lvlib). If you create the libraries in the project you created and move VIs into the library within the project (dragging the VI into the lvlib like a virtual folder in the proejct) then LabVIEW should be able to handle that without you needing to relink things.

When you build that library into a packed library you can right-click the library in the project and replaced with the packed library but I'm not sure when that feature was implemented. I would also make sure that whoever requested you move code into packed libraries has good reasons for doing that.