Should vi.lib be a reserved folder?

[CharlieD]

Hi All,

After a long hiatus I am trying to come back up to speed in LabVIEW.  Last time I used LabVIEW (version 7.x) it was recommended that the vi.lib folder be used only for NI libraries.  Is this still the case?  I am assuming the user.lib folder should be used for user installed libraries, correct?

TIA,

Charlie 

[GerdW]

Hi Charlie,

Yes. And yes! 😄

Spoiler

You should think about using a source code control system like SVN or GIT. This way you will try to keep all your sources in one main folder (atleast that's what I try to) for easier committing and checking out…

[Hooovahh]

What I've been doing for our internal reuse that gets installed in user.lib, is I set all the VI's to locked before creating the package.  Then the user can use the function and look at it, but by default can't edit it.  If I want to edit it for a test I can unlock it (no password) but it is a simple barrier to help other developers know not to try to edit it since it is somewhat system level code.  I've also experimented with setting the files as read-only after install, but sometimes edge cases are seen when the VI needs to save, and even with separate compiled code it will want to save the file which it can't.  This was years ago and maybe this was a bug that has since been fixed.  This is all done using the Pre/Post Build/Install in VIPM.

[billko]

I'm feeling like such a dinosaur with the old CLD badge...

[Gregory]

Here you go Billko 🙂

https://acclaim-production-app.s3.amazonaws.com/images/7c5d31f5-2069-4618-ba59-b710c2b6bbe4/CLD.png