Programmatic Build does not update tags in Project

[dblk22vball]

I am trying to get a build script going, and I use the destination folder format with the tag [VersionNumber] in the Primary Destination Path (http://digital.ni.com/public.nsf/allkb/617928B8E8DE3B6C86257CC400429194)

What is happening is that when I do my programmatic build, the lvproject only "remembers" the last build I manually did through the project itself, instead of the programmatic build.

for example, say I right click on my executable build specification, select "build".  My build will run, complete, and then all the files will be stored in the folder builds\EXE 1.0.0.0.  The flag "Auto Increment" is set to True. 

Now, I run my build script 5 times.  I will have folders EXE 1.0.0.1 through EXE 1.0.0.5.  I open my exe build specification in the labview project, navigate to the "Version Information" page, and the Version Number correctly shows 1.0.0.6 as the next build number.  So my build script is updating the build specification with the correct auto increment, and I have verified that LabVIEW is creating the correct files in the correct folder.

But, when I go to the build specification, right click and select "Explore", LabVIEW opens the EXE 1.0.0.0 folder, instead of the EXE 1.0.0.5 folder.

The consequence is that when I do an installer build, LabVIEW thinks that the 1.0.0.0 build was the last build, so the incorrect exe is copied into the installer.

Has anyone run into this issue with programmatic builds?

[Michael Aivaliotis]

So the main problem is getting the installer build script to get updated with the correct EXE build. I wonder if there's a way to signal that change to the installer script.

I've never seen this issue. However, I usually just programmatically run the installer build script right after the EXE build script and it works every time. Do you have the project open while doing all this?

[dblk22vball]

I was able to get it working.  Basically, I need to "auto increment" myself and manually set the destination path.

It appears that the API does not handle the [VersionNumber] tag properly, but no error is thrown.

I have been in discussion with NI application engineering, so hopefully this will be fixed.

[dblk22vball]

NI has created a CAR on this topic, as it appears it is a bug in the Build API.  FYI - CAR 724207

[Neil Pate]

I have seen a similar issue quite often with LV2015. When I right click on a build and explore it regularly takes me to the wrong build directory, usually a totally unrelated project. I do not do any programmatic builds.