LabVIEW CLI Update v1.5.1 and Question About Bitness

[James_McN]

Hey Folks,

Firstly I've just posted an update (v1.5.1) that fixes a couple of issues which were broken custom exe support and a crash if you send a message with zero bytes of data. Get it https://github.com/JamesMc86/LabVIEW-CLI/releases/tag/v1.5.1

Also I've found a way we can detect if the version of LabVIEW we want is open so we can potentially add an option to auto-kill it. Problem is it depends on LabVIEW CLI being built for the correct target bitness (32bit or 64bit). I can look into supporting both but how many people are running on a 32 bit OS now? Comment here or at https://github.com/JamesMc86/LabVIEW-CLI/issues/34

Cheers,

James

[WireWeaver]

Thanks for the update James.

---

@James_McN wrote:

I can look into supporting both but how many people are running on a 32 bit OS now?

---

I don't think this consideration should be limited to OS. Some users run 32-bit LabVIEW on 64-bit Windows because of the need to support 32-bit toolkits or dlls.

What API are you looking at that's 64-bit only? What about calling GetProcessesByName, and then looking at Process.MainModule.FileName for each process to see what versions are launched?

-Trent

[James_McN]

Exactly what I am looking at. However if a process is 64 bit (i.e. a 64 bit LabVIEW) it causes an exception when you call MainModule from a 32 bit process so 32bit LV on 64bit OS works but 64bit LV doesn't.

I'm inclining towards trying to support both. I would have to build a separate installer for each platform and then the post-build action that performs the install can decide which to install. Just need to understand how to set this up in Visual Studio.