open reference path LV2009 new syntax ?

[VdG]

Hi,

i just switched to LabVIEW 2009 and i have some new issues with the open vi reference function. My application use a lot of dynamically called vi and some subpanels too. It works well in the programming system, but not when compiled in a stand-alone executable (that was not the case in 8.6.1). I found that the troubles come from the paths feeding the open vi reference function. It looks like now it use more complete path, including the project name or some library name...Where can i find the exact syntax to use in these both cases (always for a stand-alone executable):

- create a reference for vis that are saved as .vi on the disk.
- create a reference for vi that are encapsulated (using the build properties) in the .exe file of the application.

Thanks,

[Norbert_B · Accepted solution]

Vincent,

please read the following excerp from the LabVIEW 2009 help in the topic "LabVIEW 2009 Features and Changes":

LabVIEW Application Builder Enhancements
LabVIEW 2009 includes the following enhancements to the LabVIEW Application Builder, which you can access by right-clicking Build Specifications in the Project Explorer window, and selecting the type of distribution from the shortcut menu that you want to create:

• The Application Builder no longer moves VIs with conflicting filenames outside of stand-alone applications, shared libraries, or Web services for build specifications you create in LabVIEW 2009. In LabVIEW 8.6 and earlier, the Application Builder saves VIs and library files in a flat list within the application and saves VIs with conflicting filenames outside the application in separate directories.

• If you build a stand-alone application or shared library using LabVIEW 2009, the Application Builder stores source files within the application using a layout similar to the directory structure of the source files on disk. For example, the following table lists the relative paths for a top-level VI, foo.vi, which calls a.vi and b.vi. C:\..\Application.exe represents the path to the application.

Path to source files Path to files in application
C:\Source\foo.vi        C:\..\Application.exe\foo.vi
C:\Source\xxx\a.vi    C:\..\Application.exe\xxx\a.vi
C:\Source\yyy\b.vi    C:\..\Application.exe\yyy\b.vi

To use the legacy file layout, place a checkmark in the Use LabVIEW 8.x file layout checkbox on the Advanced page of the Application Properties, Shared Library Properties, and Web Service Properties dialog boxes. LabVIEW enables this option by default for build specifications you load from previous LabVIEW versions.

• (Windows) The .NET interop assembly build specification allows you to build and distribute VIs in a LabVIEW project as .NET interop assemblies. Right-click Build Specifications in the Project Explorer window and select New».NET Interop Assembly from the shortcut menu to display the .NET Interop Assembly Properties dialog box.

• The Build Application from VI dialog box allows you to build an application from the VI you are currently editing. 

hope this helps,

Norbert 

[VdG]

Thanks Norbert,

this helps a lot. I have to try some options versus some others and find out what's the best solution for me.