how are VIs stored in 2010 .exe files?

[Faraclas]

Using the 8.x file structure, the VI's were all packaged such that you could access them with <Path>\<Application.exe>\<VIName.vi>.

I just converted a project using 2010 and am trying to use the new file layout.  However, it seems that the VIs are in new locations.  Is there documentation for how this new file stucture is organized?

[Starla_T.]

Hi Faraclas!

I'm a little unclear by what you mean by the new file layout.  Are you talking about the location of the files in a project you built?   Or are you talking about the location of the LabVIEW VIs?

Project file organization is user defined. When you build your project and installer,  you can define the file organization and location.   

If I misunderstood your questions, please feel free to clarify.  

Best Regards!

Starla T. 

[altenbach · Accepted solution]

Maybe this will help?

[Faraclas]

This is a great start and hopefully will solve the issue.  The followup question to this would be where does this hierarchy start and how is it applied to the files in the .exe.

For example, lets say I have the following:

C:\AAA\VI1.vi

C:\AAA\VI2.vi

C:\AAA\bbb\VI3.vi

C:\AAA\ccc\VI4.vi

C:\BBB\VI5.vi

D:\DDD\VI6.vi

Z:\DDD\VI7.vi

and suppose VI2.vi is the top level VI in App.exe.

Is the file structure in the .exe:

...App.exe\AAA\VI1.vi

...App.exe\AAA\VI2.vi

...App.exe\AAA\bbb\VI3.vi

...App.exe\AAA\ccc\VI4.vi

...App.exe\DDD\VI6.vi

...App.exe\DDD\VI7.vi

How are files on different drives mapped to the .exe?  What is the least common path used?

It would be awesome if NI could release an ".exe Explorer" tool to open a .exe and report back its file hierarchy.

[gmart]

Here is some additional information:

http://digital.ni.com/public.nsf/allkb/EEE8A5650DAC28558625762F0070A384

http://zone.ni.com/reference/en-XX/help/371361G-01/lvconcepts/build_checklist/

[Faraclas]

This offered some additional clarrifiaction.

http://zone.ni.com/reference/en-XX/help/371361G-01/lvconcepts/build_checklist/

Howver, the question still remains on how:

C:\Source1\V1.vi

C:\Source1\V2.vi

C:\Source2\V3.vi

D:\Source3\V4.vi

D:\Source3\333\V5.vi

Z:\Source4\V6.v

will be mapped..

[iZACHdx]

Hello,

Have you tried any steps to figure this out on your own other than reading the documentation? As was mentioned previously, if you have upgraded from LabVIEW 8.6 or previous, the file structure has since changed. Without having to resort to decoding some of the documentation on this, the best method is to simply try things out. This function is a very useful tool: http://zone.ni.com/reference/en-XX/help/371361E-01/glang/current_vis_path/ . If you need to test things, create your main VI, a test subVI at your desired file path location, and build your executable. When you do this, display the output of the Current VIs Path (resulting from calling your subVI) on your main VIs front panel. Often it is more efficient to just try things out and the answer will become obvious.

-Zach

[Faraclas]

Using the realitve file paths works great for VIs withing the same source hierarchy.  This is actually pretty neat as now I no longer have to switch out paths for runtime vs development environement.  (I'm sure that was the intent).  I think a little more documtnation needs to be written for how the file structure is organized when VIs from many different source tree hierarchies are used.