Control Setting doesnt update for Numeric Input in Distribution build

[akadolph]

I made an update to a Control Setting (increase maximum value) for Numeric Input on a UIR panel. After building and running, I am able to verify the new maximum value works within the Numeric box. But when i do an distribution build, install on a different computer (our test computer), this setting does not change. So I am developing the LabWindows program using my 64bit Win 7 machine but then i will install it on our lab test computer (32bit Win 7) because it has the DAQ card in it. 

I have installed the program on my computer and another one (64bit Win 7) with no issues. Its when i install it on our lab test computer (32bit Win 7). I have also checked to make sure that i specified the correct Configuration (Release 32bit) because LabWindows errored when i tried to load 64bit release on a 32bit machine (makes sense). I reloaded the latest LabView Runtime libriaries (2015) and that didnt fix it either.

I have a tried a few things, I changed some text in a menu, just to verify the distribution build was updated with that specific UIR file. That worked. I decided to change a different numeric box, to see i could change that maximum value. That didnt work either. I am not sure its an issue with the GUI or software code. I think it has to do with a setting during the distribution build. It seems like its loading an older version onto our test computer. Now the test computer has a previous revision of the program where the other computers i tried, were loaded from scratch.

[TheCaptain]

Akadolph,

Have you tried deploying the application to a new computer and checking to see if the new maximum appears there? When you moved the updated distribution to your test machine, did you remove the previous distribution?

[akadolph]

Yes - I have successfully installed it on three seperate computers, and the new maximum values appear there. For the lab test computer, i have uninstall previous versions prior to a new installation with no luck. I may need to uninstall all NI drivers and runtime libraries and then start fresh.

For now, I dragged over the folder with all the source code files and the run the application through there. It seems to run fine with the changes, its ok for now. But long term, i would like to know why the deployment build does not work properly on that specific computer.

[TheCaptain]

Akadolph,

What NI software do you have installed on the test computer? And just to verify: this was the exact same distribution that you successfully installed on 3 computers and the test computer?

[RobertoBozzolo]

Just a guess: may it be that you have compiled the application with "Embed project UIRs" option enabled and you have simply updated the UIR on the test PC? In this case installing the complete application from scratch on a fresh PC will inherit the modifications, while simply copying an updated UIR on the test computer won't have any effect since the UIR file is not used.

[akadolph]

I uninstalled all the NI drivers and runtime libraries from the test lab computer. Then i re-install the deployment build and everything succesfully installed. The new changes to the UIR panel did port over. Also, on this build i did not select the "Embed Project UIR" option. I am not sure if that impacted it, i could try a build with that option selected, just to rule things out. But the program is now running correctly.

Thanks.

[RobertoBozzolo]

"Embed project UIRs" option impacts in that even for simple modifications in the UIR file that do not affect the code (e.g. align controls) you must recompile and deploy the whole project to have the change appearing in the target PC.

With .UIRs separated from the .EXE you could simply deploy the modified UIR to update the application. On the other hand, if the change implies a code modifications and you don't distribute the .EXE you will get errors while executing the application.

It's up to you to decide whether to use this option or not, ther is no "better" choice in my opinion, but you must be aware of all the implications and operate accordingly.