Standalone add-on to multiple projects

[battler.]

Hi guys,

I've written a standalone module which I want to include as an add-on to several projects.  The module consists of around 100 VIs itself.

Question is how to maintain the module for inclusion into other projects (to include in exe build).

I don't want to keep multiple copies of the module.

I have started to use libraries but I don't think they're going to work.  Any ideas on the best structures (project and file) to achieve (a) portability of module into other projects; and (b) maintainability of module.

Thanks.

[GerdW]

Hi battler,

I keep all those "modules" in my user.lib and use them in any project I need to.

Then the "user.lib"-VIs will appear under "Dependencies" in your project tree…

[.aCe.]

Plug-in architectures using packed libraries, here is an interesting one: https://decibel.ni.com/content/docs/DOC-19176