I am using a CLI command to build two build specifications in sequence. This command will later be used with a Jenkins server to automate the build process.
LabVIEWCLI -LogToConsole true -OperationName ExecuteBuildSpec -ProjectPath "%cur_dir%\LVProj.lvproj" -BuildSpecName "BuildSpec"
LabVIEWCLI -LogToConsole true -OperationName ExecuteBuildSpec -ProjectPath "%cur_dir%\LVProj.lvproj" -BuildSpecName "BuildSpec2"
The issue is that the program uses XControls, and the user has to manually "Apply Changes" to one of the XControls on startup of the project to fix the error (below). This isn't an issue normally, but the ExecuteBuildSpec command launches LabVIEW and tries to build the first build specification with the error, causing the overall build to fail.
Is there a way to "Apply Changes" programmatically with a command/VI? Alternatively, what can be changed with the XControl to stop the need for applying changes?
Solved! Go to Solution.
There is this:
But after you manually Apply Changes, just save all the VIs that have instances of the XControls and that should eliminate the need for future 'Apply Changes'. If that isn't the case, then you might have some circular dependencies.
Do any of the XControls have dependencies on LV classes? That can cause headaches. If you do have such dependencies, there are ways to eliminate them.
The XControl in question has a dependency on the main view class. It will need re-working in the future, but for the time being the method you posted is a good workaround, thanks.