Problem executing dynamically loaded plug-in .vi's from .exe in run-time environment.

[MikeTex]

Jarrod,

Oops! It just occurred to me that you're referring to the plug-in's project, not the main app's project. Let me give that a try.

I think I'm losing my mind on this project!

Mike

[MikeTex]

Hi Jarrod,

Ok, I tried the workaround with the plug-in.

Only 4 small files were created with the Source Distribution. I've enclosed the screen shot.

The main application starts fine, but the plug-in still fails. When I click the "list errors" arrow I get:

"The VI is not executable. The full development version of LavVIEW is required to fix the errors."

Mike

Message Edited by MikeTex on 05-16-2006 05:35 PM

[Jarrod_S.]

Hi Mike,

I really hope we should be getting closer to the solution. One last setting to check that I didn't see in your screenshots. Under the Distribution Settings category for the Source Distribution, you should have Exclude vi.lib unchecked and Disconnect Type Definitions and Remove Unused Polymorphic Instances unchecked.

That last item is what actually determines whether LabVIEW includes an abridged library with only the referenced files or all the files in the library. If it's unchecked, LabVIEW will include the whole library. I'm honestly not sure, though, why no VIs except the main VI were included in your build. Could you perhaps zip this project and post it?

Message Edited by Jarrod S. on 05-17-2006 12:54 PM

[MikeTex]

Jarrod,

Ok, I've got some good news. It works! 🙂

I unchecked "Exclude vi.lib" and the distribution grew tremendously large. And by large, I mean super large. The original 10kb "Mean Test.vi" single-file plug-in grew to 1600+ files totaling over 30mb. Also, I had to check "Single Destination" because "... Preserve Hierarchy" created a strange structure that I couldn't get working. I might revisit this later when I understand what it's doing a little better.

At this point I'm just happy that it's running. This workaround is kind of painful ... do you expect the R&D group to produce a solution to the root problem in the future?

I'll need to figure out a way to cleanly package all the files for each plug in. Perhaps a folder per plug-in. I suppose that I'll be including a near complete copy of vi.lib for every plug-in. Oh well.

Jarrod, I really appreciate that you took the time to work through this with me.

Mike

[Jarrod_S.]

Hi Mike,

I'm really glad we got at least something working! I built a source distribution on my side as well, and it did take a while. The issue is under investigation by R&D. Beyond that, I don't know any more details.

At this point I can recommend one strategy to minimize the number or size of future source distribution builds. Unless additional libraries from vi.lib are added (for instance, something other than NI_AALBase.lvlib), you can check Exclude vi.lib for future source distributions to only copy your VIs. There's no need to duplicate VIs. You might consider installing the vi.lib files under C:\..\LabVIEW 8.0\vi.lib with the same hierarchy on the target computer so that all future distributions can expect to look there and find the necessary files.

[lmtis]

Has NI found the root cause of this error?  I have an application that was originally written in LV 8.x that I have just modified with LV2009.  I am now getting the same error reported in this thread.  In the Additional Exclusions section of the Build Specification I unchecked "Remove unused members of project libraries" and "Remove unused polymorphic VI instances", but I am still getting the "Missing subVI NI_AALBase.lvlib:Mean.vi" error.  I am not doing anything fancy, I just have a project that has 3 VIs that use mean.vi.  It worked fine in LV8.x, but not after building with LV2009.  I even tried replacing each instance with mean.vi, to no avail.