extra folder added into the current vi's path function when compiled into executable

[D@vidO]

Good to know, thanks!

Looked a bit further, and it seems LV2013 autochecked "Use 8.x file layout" when opening the LV 8.6 project.

LV 2015 did not.

So this explains why I got different results.

/David

[TeraTech]

@TegtmeierD: I realize this is an old thread, but hope you're still subscribed, because I have exactly the same problem but it is not clear how you used the Application Directory function to resolve the extra folder issue.

---

TegtmeierD wrote:..." use the "Application Directory" function and it does resolve this issue.

This is what I found:

Using Application Directory vi at development time gives you: c:\lvproj-folder
Using Application Directory vi at runtime time gives you: C:\exe-install-folder
However (and this is my point of question) to actually access the sub folder at run time (inside the exe) would need to be:

C:\exe-install-folder\application.exe\subfolder
NOT following: C:\exe-install-folder\subfolder

Are you programmatically inserting the "application.exe" name into the path?

[crossrulz]

---

@TeraTech wrote:

@TegtmeierD: I realize this is an old thread, but hope you're still subscribed, because I have exactly the same problem but it is not clear how you used the Application Directory function to resolve the extra folder issue.

---

TegtmeierD wrote:..." use the "Application Directory" function and it does resolve this issue.

This is what I found:

Using Application Directory vi at development time gives you: c:\lvproj-folder
Using Application Directory vi at runtime time gives you: C:\exe-install-folder
However (and this is my point of question) to actually access the sub folder at run time (inside the exe) would need to be:

C:\exe-install-folder\application.exe\subfolder
NOT following: C:\exe-install-folder\subfolder

Are you programmatically inserting the "application.exe" name into the path?

---

This is one of the reasons I always say to use Application Directory to find something outside of the executable (config files, data files, etc) and use Current VI Path to find something inside of the executable (almost always other VIs).