application builder API and ni packages in LV2017

[psmorris]

Not sure if anyone's come across this before - I have flagged it with support in the UK...

If you use the application builder API to change the build specification version of a package build spec in a LabVIEW 2017 project, although the "build specification version" is updated (checked by using the application builder API to query the version) the actual package version doesnt get update - open the build spec in the project, go to the "version information" page and it does not get changed by the builder API code...

Having played around with the build spec tags it appears that (in 2017 at least) the package build specs have a different tag for version number (PKG_version and PKG_buildNumber)... workaround is to use VI server to set those, but in LabVIEW 2020 the application builder API works fine and "as expected" - so I suspect this is an oversight in the 2017 package builder add on somewhere.

Cheers

Paul

[CL_eisenwr]

We had run into this a few years ago as well in LabVIEW. It was bug until it was fixed in LabVIEW 2019. This Github repo should have an example of how to work around the issue.

Edit: Repo is in LabVIEW 2018, so I back saved it to 2017 and attached it.

[psmorris]

Ah, ok, so its "expected behaviour" - or at least a known about bug...

That github repo is for LV2018, but I worked around already in 2017 by figuring out the tags... (probably what's done under the hood in that repo!) Most of our work will jump to 2020/2021 shortly anyways, so we'll either use my workaround in 2017 or use it working properly in the newer version!

Thanks again

Paul