How to produce exit code in standalone LabVIEW application

[E.P.]

Hello everyone,

How does one produce an arbitrary exit code on exit from a standalone (compiled with Application Builder) LabVIEW application, similar to what C-language exit(err_code) function call does? Thank you. -Ed

[tst]

What does this C function do?
Do you want to send a code somewhere when you exit your application? If so, where to?

[dht]

Hi - if the question is how to exit labview correctly after .exe produced using application builder.
The recommended method is to drop a LABVIEW EXIT (QUIT ) vi onto your wiring diagram, and wire it accordingly.
The vi is in the application control palette.
regads dht

[JeanPierre]

The Event structure has an "Application Exit" event that is triggered when the user tries to exit the application. Trap this event and execute any code you need to from there.

[JeanPierre]

Sorry, I first understood that you wanted to "execute" some code at exit, instead of outputting an error code number.

[chrisger]

Hi there,

if you want to use %ERRORLEVEL% in your calling process of the LV-App call

void _exit(long code);

from MSVCRT.dll in your System32-Folder.

But remember: that kills your App immediatly!

best regards
chris

[E.P.]

---

@chrisger wrote:
Hi there,

if you want to use %ERRORLEVEL% in your calling process of the LV-App call

void _exit(long code);

from MSVCRT.dll in your System32-Folder.

But remember: that kills your App immediatly!

best regards
chris

---

Thanks Chris! Do you know if that would be considered a "clean" (normal LabVIEW) exit? Would LabVIEW be able to do whatever "house keeping" it does upon regular application termination? -Ed

[chrisger]

/*
Thanks Chris! Do you know if that would be considered a "clean" (normal LabVIEW) exit? Would LabVIEW be able to do whatever "house keeping" it does upon regular application termination? -Ed
*/


hello

well, i would say "no". the call of exit kills the process, i.e. the instance of your LabView RTE. the only things cleaned up by the call of exit in a standard c-app are those initialized with atexit (if my memory hasn't left me). so, in your place i would clean all things opened by my self (files, DAQ, etc) BEFORE the call of exit, but the things opened by the LabView RTE (services etc.) may be just killed. but, for more info regarding exit visit msdn.com.

hmmm..
if you want to be save, you could create a textfile containing the errorcode at the end of your app, exit LabView RTE with the LV-Exit function, and then read the textfile in your batch (there are some batch-commands for such purposes)!

let us know
chris

[THailey3]

Hi Everybody!

I second what dht said and would use the Quit LabVIEW VI to exit a LabVIEW executable running with the Run-Time Engine. This will provide the usual "house keeping" rather than just killing the application.

Travis H.
National Instruments