search

JamesMc86 / G-CLI

A proxy mechanism allow LabVIEW programs to easily write out to the command line.
BSD 2-Clause "Simplified" License
71 stars 19 forks source link

TypeInitializationException with G CLI 2.4.0.5 #141

Closed negentropicdev closed 1 year ago

negentropicdev commented 1 year ago

image

Not sure how to progress. I'm just trying to run a VI that outputs the arguments to a dialog to test a call. I'll start poking around the source code.

negentropicdev commented 1 year ago

I've tried with verbose flag to get additional info and nothing additional gets displayed before the exception stack.

negentropicdev commented 1 year ago

Here's the hierarchy I have in regedit WoW node (all community edition installs), are the folders besides 20.0, 22.0, AddOns, and CurrentVersion causing an issue?

negentropicdev commented 1 year ago

(Helps if I paste the screenshot) image

JamesMc86 commented 1 year ago

I explicitly exclude AddOns and CurrentVersion but not Common so that may be the issue.

I'm gonna be a pain and ask if you can try 3.0 which I've just finally pushed as a release! You can get it from https://github.com/JamesMc86/G-CLI/releases/tag/v3.0.0 and this part has been rewritten.

I suspect it may have the same issue as it also won't filter out common so it will probably need patching.

Probably better to match on a pattern of dd.d where d is a digit rather than filtering out others.

negentropicdev commented 1 year ago

Until NI changes their versioning scheme again ^_^ Probably want to test every group for the Path subelement you're looking for.

I'll give the 3.0 release a shot and report back

negentropicdev commented 1 year ago

The rust build (3.0) does successfully launch LabVIEW.

negentropicdev commented 1 year ago

However, the VI isn't run once opened. I've also tried making sure Run when Opened is set which didn't help.

negentropicdev commented 1 year ago

It seems to be related to 2020 not having the ability to remember the run when opened allow preference. I'll dig into that some more.

negentropicdev commented 1 year ago

Definitely looks like a LabVIEW limitation. If I put the VI in vi.lib then it runs on launch. Which ultimately would be the destination anyways so I think I'm good here.