VI Name collision in Built application and the Plug-in VI

[தமிழ்நேரம்]

Issue:

Dynamic Launching of a VI works fine when the plug-in code is launched from the LabVIEW source code.

When the Application was build it fails to launch the VI. Upon debugging I found that I am reusing some of the SubVIs in the plug-in VIs that is part of the EXE. I tried renaming and re-linking of those Vis for the Plug-in VIs it works fine.

Solution:

           Similar to Name spacing provided by Lvlib files. Add an additional option in the Exe build spec, to add a name space for the application this will rename all the VIs as "my project:main.vi, My project:test1.VI" etc inside the Exe. This will resolve the naming issue created by the LabVIEW runtime engine. So a plug-in VI can reuse the test1.Vi from the Source code.  

[AristosQueue (NI)]

This feature already exists. In the Build Specification dialog, go to the Destination settings page and click the checkbox for "Add files to new Project Library".

[தமிழ்நேரம்]

Hi Aristos,

                 Thanks for the pointer. I have tried that option, it renamed the file names inside the exe(checked using hex editors) but it still fails to lanch the dynamic plugin VI. very simple example will be try using the merge error provided by ni in both the exe and in the plugin VI. the plugin will fail to launch.

                   May be I should not call this as an idea now since the feature is already available, I will call it as a bug.

[தமிழ்நேரம்]

Even I tried the "Apply prefix to all contained items" option in the "source file settings" , this also renamed all the VIs inside the exe, but the runtime engine fails to launch my application that uses the merge errors Vi.

[Todd S.]

This feature already exists in LabVIEW

[G-Money]

I am changing the status from Completed to Declined because Completed should only be ideas that R&D see on Idea Exchange, actively developed on it based on the idea here, and it was added to the product.

[G-Money]

This feature already exists in LabVIEW