LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Application Directory in RTEXE

My RTEXE builds are having Application Directory return a path WITHIN the rtexe instead of the folder containing the rtexe (presumably it's not recognizing being built into an app and is instead returning the folder containing the top-level VI?)

 

Has anyone else seen this? Is this somehow expected behavior?

~ Helping pave the path to long-term living and thriving in space. ~
0 Kudos
Message 1 of 5
(98 Views)

I am resorting to this to get my expected behavior:

IlluminatedG_0-1741629543753.png

 

~ Helping pave the path to long-term living and thriving in space. ~
0 Kudos
Message 2 of 5
(96 Views)

I don't have experience with real-time, but I ran into a similar problem when I used LabVIEW to build a DLL. I wanted to use "Application Directory" to get a path to the DLL, but it gave the path to whatever had loaded the DLL (could be python.exe for example). I ended up using "VI Path" and stripping the path to the DLL location.

 

All this to say, I think continuing with your work around is the best thing to do.

0 Kudos
Message 3 of 5
(55 Views)

I should say that this has changed behavior across builds. Used to work fine.

 

Your DLL usage is entirely expected; it says it will point that the path of the executable... not DLL.

~ Helping pave the path to long-term living and thriving in space. ~
0 Kudos
Message 4 of 5
(36 Views)

I have an rtexe developed in LabVIEW 2021 where I am using a very similar workaround to get the application folder. 2020 behaved the same if I remember correctly. Not that I expect this behaviour, but it seems to be consistent, at least.

0 Kudos
Message 5 of 5
(24 Views)