Versioning Packed project libraries

[littlesphaeroid]

Has anyone tackled the problem of managing versions of packed project libraries? How can I ensure that the libraries being used by my application are the newest? How can I save and deploy libraries with the same name in a way that makes it easy to see if the correct version is in use. 

With dynamically called libraries, I have put version numbers in the library name (since LV2015 this must be set before the library is built). With packed libraries that are dependencies, this is not an option. 

Does one simply maintain a table of the most recent versions of the code in use and check against that?

[NIMarketing]

Based on some research:

• If some people are unfamiliar with packed project libraries and their difference with source distribution
  • Packed project libraries are built (run-time compatible) which do not require the development environment and are typically single file making them easier to deploy. However they are built to a specific version of LabVIEW. One of the main reasons to choose this method is versioning (the files have version information) as well as ease of deployment (single file).
• If your concern is about the VIs within the packed project libraries, here is Some information about  Updating and Patching VIs in LabVIEW Packed Project Libraries
• Otherwise, NI does not have a version manager specifically for packed project libraries. There is a forum post regarding how to obtain the version of a packed library file programmatically. I would think the easiest way is to, as you had suggested, keep track of it on your own.
  • There is an Automatic Version Manager (AVM) for LabVIEW by System Automation Solutions LLC, but I have not tested it out for packed project libraries. So this could be a possible solution.
• There may be some people who have made their own version manager, so if anyone has any suggestions, feel free to help out

Hope this helps! Good luck!

Parul M.

Applications Engineer

National Instruments