Jump to content

Software Reuse Library Structure

Recommended Posts

I was wondering if anyone would be be able to comment on the structure, in detail, of their reuse library.

Using VIPM, I am interested to know how other people structure theirs.

I would like to make sure I am going down the right track wrt structure.


I have a bunch of questions like:

  • Where do you place your packages in the LabVIEW folder hierarchy?
  • Where do you place your packages in the palette?
  • Do you separate your library, toolkits and drivers in the palette (if you make a distinction at all)?
  • Do you use VIPM to release candidate VIs in packages before officially releasing them?
  • If so, do you version them whilst using same namespace (e.g., or use different namespaces to the final release (candidates = _company_lib_name_candidate)?
  • Do you stick them in a different place in the folder and palette hierarchy?
  • Are there any caveats you have come across whilst building your library hierarchy?

In an effort to find information I found some great comments here that I have been reading. If anyone has any other information please post

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

By using this site, you agree to our Terms of Use.