07-18-2025 01:16 PM - edited 07-18-2025 01:18 PM
I inherited a large LV project with both Windows and RT targets. This code base can be built and deployed to different test cells - each cell has a unique subnet that the RT and Windows apps talk to each other over. The issue I have is that there are many Shared Variables in the code which do not use programmatic access and so they are tied to whichever test cell's IP address is currently specified for the RT target in the LV project.
This means if I want to update the application version running in each cell I have to first set the correct test cell IP address on the RT target in the LV project, open the windows exe build spec, click on Shared Variable Deployment, hit save, and then rebuild the code, and I have to do this for every test cell even though nothing in the actual logic has changed. This results in days of wasted time just building the same application over and over again, etc.
I can eventually convert all Shared Variables in the code to have programmatic access so they can load the IP address at runtime, i.e. a "build once, run anywhere" architecture. But I am afraid that down the road someone will forget this best practice and drop a non-programmatic access SV onto a block diagram and cause difficult-to-debug runtime issues. Is it possible to write a script which finds all non-programmatic SV instances in a code base? I would then trigger this script to run every build.
Perhaps there is another way to approach this problem. Any input appreciated.
07-18-2025 04:04 PM