Versioning for Packed Project Library (PPL)

[Norbert_B]

Currently, the version of the packed project library (PPL, extension .lvlibp) is defined by the build script which creates the lvlibp.

It would be nice to have an option there to "hook" the version of the lvlibp to the version of the lvlib, which is used for the PPL.

The advantage is to match the developement version of the lvlib to the deployed version, the PPL.

[sekel]

A really handy feature would be to add an additional tool to the LabVIEW packed library palette that allows the user to easily access some of the packed library information. Specifically, the version, but documentation and other info would be handy. This function would be operational cross platform (including real time). 

PPLs are really providing some next level functionality and a few more built-in tools to help manage them would be great.