.net DLL build executable

[Jorge_Amaral]

Hello All,

I've the following situation... I'm using a .net DLL to control a certain device in labview 8.5. All it's working  correctly on my computer or any other that has Labview installed (obviously). But now i wanna deploy my application. So:
1 -  i've installed labview runtime
2 - copy my executable to the destination folder with all the dll's necessary on this same path

And the result it's a common window that repeats lots of times the sentence "the vi is not executable".

What is the problem of my deploying procedure?

[RobBoyer]

Hey Jorge,

I've seen that error message before ("thi vi is not executable").  My case was a little different, and I'm not sure I completely understand what your situation is, but you still may want to try this.  In my case, VIs that were working perfectly suddenly crapped out when I tried to build them into an executable.  In the end, I discovered the root cause to be an ActiveX function call that needed to be relinked to work with a control that I'd bumped to a higher version of the ActiveX control.  Anyway, try holding down shift and control and then clicking the run button on all your top-level VIs - if there are any underlying issues, this will force a re-compile which could help you find the root cause of the problem.

Hope that helps,

Rob

[rolfk]

---

@jorge Amaral wrote:
Hello All,

I've the following situation... I'm using a .net DLL to control a certain device in labview 8.5. All it's working  correctly on my computer or any other that has Labview installed (obviously). But now i wanna deploy my application. So:
1 -  i've installed labview runtime
2 - copy my executable to the destination folder with all the dll's necessary on this same path

And the result it's a common window that repeats lots of times the sentence "the vi is not executable".

---

In addition to what was already mentioned, where do you put your .Net DLLs. The only two places they can possibly work on other systems are either in the same directory as your executable is located or in the GAC. The last requires however that you have strongly named .Net Assemblies.

Are you absolutely sure that you have all .Net DLLs and possible other DLLs copied from your development system to your runtime system? A single missing statically linked DLL will fail the load of any other DLL eventually resulting in LabVIEW getting told the .Net (or other) DLL couldn't be loaded and giving you in the end that message.


Rolf Kalbermatter