Any way to look into a compiled LV exe file

[alex.]

I want to know the file name and path inside it.

Can it be done by developer tools?

[Kallis]

If you are using LV 8.0 or above, you can  enable debuging while you create the exe. After this use the Operate>>Debug Application or shared library to debug the executable. Hope this helps.

Kallis

[Philip_Courtois]

I'm not sure what you mean with "the file name and path inside it", but you can get the names of the VIs that the executable was created from and event the front panels (if they were saved with the executable) by following the procedure described here.

Good luck!

[rolfk]

---

@Philip Courtois wrote:
I'm not sure what you mean with "the file name and path inside it", but you can get the names of the VIs that the executable was created from and event the front panels (if they were saved with the executable) by following the procedure described here.

Good luck!

---

Unless you use LabVIEW 8.20 for Windows. That has changed the way the LabVIEW VI library is embedded into the executable stub in conjunction with the required support for signed executables for Windows Vista and all the external accessible LabVIEW methods to locate the VIs in VI libraries have been left on purpose to not know how to look for this new way of embedding the LabVIEW code in an executable. So for LabVIEW 8.20 executables the VIs inside are really unaccessible for anyone not having inside knowledge of the LabVIEW kernel itself. I haven't even bothered to look unitl now how they may have done that.

Rolf Kalbermatter

[Philip_Courtois]

Rolf to the rescue!!!

My bad - I wasn't aware that the old "exe-to-llb" trick didn't work in version 8.20. Well, I guess it's better like that anyway - it means that an executable file now offers more protection of the source files than before.