|LabVIEW 2016 Help|
|LabVIEW 2017 Help|
|LabVIEW 2018 Help|
|LabVIEW 2019 Help|
|LabVIEW 2020 Help|
Consider the ways in which you might use an LLB before you decide whether to convert it to a LabVIEW project library. LLBs and project libraries serve different purposes and are not mutually exclusive.
For example, you might want to convert a self-contained collection of files that serves as an application programming interface (API). Converting an LLB to a LabVIEW project library provides several advantages. You can perform source control operations on individual items that the project library owns. However, you cannot perform source control operations on individual VIs in an LLB. You also can configure access options on items that the project library owns so they are public or private.
If you convert an LLB to a project library, you lose the ability to set a top-level VI to run automatically when you open the LLB. You cannot mark a VI as top-level in a project library. For example, you might not want to convert an LLB that consists of VIs that behave as a single application, which runs automatically when you open the LLB. Consider organizing this type of LLB in a LabVIEW project instead.
If an LLB consists of a single top-level VI and a collection of subVIs, consider adding the VIs in the LLB to a project library. Save the project library file (.lvlib) inside the LLB with the VIs. In the project library, set the access for the subVIs as private. Organizing the files in this way allows users to run the top-level file in the VI without having access to the subVIs.
Complete the following steps to convert an LLB to a project library.