Advice on redistributing VI's in a library

[DBISI]

Hello,

I would like to share my commonly used VI's between projects and between computers easily, so I am building a library. I had done this years ago but I no longer have that code and I forgot how I did it, and I remember it being a chore. I have been looking up tutorials all morning and I am still confused on what the BEST method is between LLB's, LVLIB's, and packed libraries.

Is one of these better than the other for including files by a simple drag and drop into LabVIEW, including a palette?

I've been trying the .llb method using this tutorial: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YIU7CAO&l=en-US

Ideally, I'd like to do something for both 32 and 64 bit LabVIEW, if possible, but I don't remember that being doable. Which is fine.

[ZYOng]

You should use lvlib for code reuse. See Sharing Code With the LabVIEW Project Library

llb and lvlibp are compiled libraries and are usually for deployment purposes.

[billko]

I wholeheartedly recommend using JKI's VI Package Manager to distribute libraries!  Makes a neat little package that separates your source from your distribution.  (You develop your library in its own folder and let the VIPM installer put the distribution in the userlib folder.)  Bonus perks - even with the free version - are that you can create menus and submenus, each with their own icons, and have them show up in the palettes, just like he native stuff.  Unfortunately, the free version doesn't include your library in the right-click "replace" menu.  But what the heck, I can live with that.

[DBISI]

Oh I like that Package Manager. Not a fan of the forced requirement of Company, but whatever.