09-09-2022 11:34 AM - edited 09-09-2022 11:35 AM
Just saw this article from Jim which sounds pretty exciting: https://create.vi/ni-and-jki-partnering-on-package-management-in-labview-d243b13ae3a6
Short summary, we will get some VIPM pro features (like vipc configuration files) for free in VIPM 2023, and LabVIEW will also ship with Project Dragon, or at least its features.
I'm hoping we don't need to be using LabVIEW 2023 to make use of these features.
09-09-2022 01:32 PM
09-12-2022 08:04 AM
Wow this is really cool. One of the lesser known (but awesome) features of VIPM is the VIPM API in LabVIEW. This allows for calling various function in VIPM from LabVIEW, like building new versions. This feature was locked away behind the pro version so I never did too much with it. But if it is included in all versions I might give it a try.
Another awesome pro feature I do use is the Pre build, and Post build VI calls. You can have VIs that do custom stuff before a build. And with this feature if you don't have the pro you previously could just run the VI yourself before making the build. But hopefully now you don't need to think about it at all.
Oh and another thing is the scanning for dependent packages. I loved that feature for dependency tracking. If you had the free version you could manually add dependencies, but you obviously needed to know the dependencies you added.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
04-04-2023 08:37 AM
Are those pre/post build actions are really within the build process? Or just something that is started (manually/independently) before the actual build process is called?
I remember there is a longer discussion about this topic on the ni forums, but I can't find again...
04-04-2023 08:47 AM
@A-T-R wrote:
Are those pre/post build actions are really within the build process? Or just something that is started (manually/independently) before the actual build process is called?
I remember there is a longer discussion about this topic on the ni forums, but I can't find again...
What you might be remembering, is that previously the Pre/Post Build VIs was a Pro feature. If you made a config and shared it, then ran it on a VIPM that wasn't pro, it would tell you that the Pre/Post Build VI isn't supported and gave you an option to abort the build, or continue without running the VI. If you did have the Pro it would actually run the VI.
I currently have VIPM 2023.1 installed set to the free unregistered edition, and it does actually run the Pre Build VI I have set. A very helpful feature for things like setting the VI description to the package version, locking VIs, setting them to read only, setting passwords, or adding any other features that VIPM doesn't have.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord