Why won't a .net dll run in a standalone executable when it runs fine in the base vi?

[sbuxton]

Hi All,

I'm using a third party dll to talk to some external hardware using the LabView graphical interface.  When I run the VI everything works fine, however, when I build a standalone exectutable the dll does not run and the program immediately stops (presumably due to an error.  Has anyone else had this issue?

Thanks

Sean

[tyk007]

---

@sbuxton wrote:

Hi All,

I'm using a third party dll to talk to some external hardware using the LabView graphical interface.  When I run the VI everything works fine, however, when I build a standalone exectutable the dll does not run and the program immediately stops (presumably due to an error.  Has anyone else had this issue?

Thanks

Sean

---

Presumably the dll appears in the build folder when you build?

[mikeporter]

What is the presumable error? That is the place to start.

Mike...

[sbuxton]

tyk007: Yes, the .dll appears in the build folder.

Mike:  The loop stops if there is an error or if the stop button is pressed.  Since the loop stops immediately there must be an error, but the error window does not pop up.

Thanks,

Sean

[Sam_Sharp]

If you are wiring the error to another node (e.g. stop terminal) then you won't get an automatic error handling popup. Have you tried putting an error handler VI/popup in your code or logging the error to disk to see the code/description of the error?

[sbuxton]

No.  I'll try that

[sbuxton]

Adding in the error handler I get:

Possible reason(s):

LabVIEW:  End of file encountered.
=========================
NI-488:  Invalid argument or arguments to function call.

[altenbach]

Is it possible that the dll depends on some other dlls that LabVIEW does not know about?

[sbuxton]

That solved it! Thanks everyone!

Sean

[ªL¡]

sbuxton: how did you solve your problem? I am having the same error and the DLL is included in the support directory of the compiled file and I am still getting the error.