jvr-ruiz/jki-.net-system-exec

Wrapper around the .NET Process classes to launch a process and listen to the stdout and stderr

jki-.net-system-exec's Issues

Non-existent working directory should be discarded to default

I misconfigured my app and the System Exe node ramped up CPU to 100% until I aborted the VI.

I suggest to add this check inside the creator and throw a warning in case the working dir is non-existent.

The sourcecode does not contain the BSD license text

I noticed that this package is listed as BSD licensed on vipm.io, but I don't think it counts unless you put the license text with the sourcecode. I couldn't find it, but do correct me if I am wrong! With the license text, reusing the code is breaking the license. Could it be added?

An example of how you could include it would be OpenG, where the license text is on the front panels.

I'm happy to have a go at doing it myself (I have LabVIEW 2018 installed and can backsave the VIs) but the package build stuff is done in VIPM 2020 so might have to ask for help on that.

---

Edit: I forgot to mention, another option is to put a LICENSE.txt with the source code (i.e. in the folder in vi.lib)

Add Exit Code

Could you please provide the exitcode of the process?
Or maybe expose the process handle?

Addition of a terminate/kill process method

Hello

It appears that the .NET process interface provides a method that will kill the running process which might be useful in some instances.

Do you think it would be a worthwhile addition to the library to expose this via the LabVIEW API?

I could submit a PR if you are interested.

Cheers

John