06-05-2020 01:27 AM - edited 06-05-2020 02:00 AM
I am trying to understand about how the path of a vi (main.vi ->as mentioned below) inside exe differs in two cases
1. when a subvi is inside same folder as main vi
Main.vi Path: E:\Test\Source code\Main.vi
Subvi Path: E:\Test\Source code\Subvi
Current VI path from exe : E:\Test\Exe\Application.exe\Main.vi
2. when a subvi is outside the main vi folder
Main.vi Path: E:\Test\Source code\Main.vi
Subvi Path: E:\Test\Subvi
Current VI path from exe : E:\Test\Exe\Application.exe\Source code\Main.vi
Why only in the second case the Source code folder is appended?
I just need to understand the folder hierarchy maintained inside the exe
I have also attached a sample test project to understand the same.(LabVIEW 2019 64-bit)
Solved! Go to Solution.
06-05-2020 03:15 AM
Hi Naga,
@NagaPonEzhil wrote:Why only in the second case the Source code folder is appended?
I just need to understand the folder hierarchy maintained inside the exe
The hierarchy inside the EXE is the same as in the IDE source folders!
In case 1 both VIs are located in the same folder, so it's ok to omit this folder into the EXE folder hierarchy.
In case 2 the VIs are located in different folders, so it's neccessary to include the folder into th eEXE folder hierarchy…
(Usually I store my MainVI in the "main" folder, while subVIs are located in folders below the "main" folder: is there a reason for you to keep it the other way around?)
06-05-2020 08:21 AM
Hi GerdW,
Thank you for the immediate response.
The reason i kept it in a separate folder is because both are different projects which i have already designed. Now i have to integrate both without disturbing the folder structure of both projects.