12-02-2022 12:59 PM
Hi all,
I installed g-cli in a vm and when running any commands I get an error. It doesn't make a difference if I try to run a vi or just run the command without anything. I'm using Version 2.4.0.5
The error I see is:
Unhandled Exception: System.TypeInitializationException: The type initializer for 'G_CLI.LvVersions' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at G_CLI.LvVersions._ScanRegistry(RegistryView regView)
at G_CLI.LvVersions.Scan()
at G_CLI.LvVersions..cctor()
--- End of inner exception stack trace ---
at G_CLI.LvVersions.get_CurrentVersion()
at G_CLI.Program.Main(String[] args)
previously I had labview-cli installed, which gave me the same result. Installation went without errors.
What might be causing this?
12-02-2022 09:02 PM
Just ran into this issue today! Have some builder PCs that were upgraded to add 2022 Q3 with RT/FPGA, as well as DAQmx/cRIO/XNET 22Q3/4 drivers, and even when the pipeline went to target the existing 2020 stack, g-cli came up with an almost identical exception.
The build machines that have yet to be updated with 2022 Q3 don't have this issue.
12-03-2022 07:25 AM
So according to the developers it's an issue with LabVIEW 2022 Q3, because of its name. Version 3 of g cli is supposed to fix this. G-CLI issue 128
Haven't been able to test, yet. But I'm sure it works.
12-03-2022 11:53 AM
OK, I just tested it and this works with v3.0.0