Drawback of packed library vs old llb

[BuzzAldrin1]

(I understand I am replying to a 7yo post)

I have the same dilemma with my current project. I am inheriting an old project tree with two large collection of support VIs (dependencies). I am considering .lvlib to include in the project (.lvproj) tree. I have noticed some weird idiosyncrasies with .lvlibp files such as somehow LabVIEW "remembers" that I created these packed libs and when I open unrelated projects (.lvproj) these unrelated .lvlibp files are being searched and loaded? I don't know how to disable this behavior in LV 2015 Developer. I move to another station with same LV version and this behavior is there. Is this a bug?

Anyway, head over to the LabVIEW Wiki site: https://labviewwiki.org/wiki/LabVIEW_Library

From what I have experienced with .llb files they are more or less "ZIPped" version of a directory. This is normally the way to create .llb files but you can the sub-VIs one at a time with the LLB Manager.To answer one of your questions, no LabVIEW only loads the sub-VI you call from the LLB.

Cheers,

Aldrin