Building Application Without Distributing Polymorphic VIs

[GeoffF]

Hi all,

We're currently deploying several LabVIEW applications that use polymorphic VIs.  I have no problem building these applications (apart from one known issue with LV8.6.1 and a bad dsoffset error - so we use LV2010 for that app).

My issue arises with the deployment of these systems.  At present, the polymorhpic VIs are copied to relevant subdirectories and deployed as they stand.  To my mind, this is messy.  It would be better if they were packaged inside the executable.

I'm sure one of the Application Builder controls allows this, but it's not obvious how to do it.  The manuals don't seem to tell me much more than the online help, either.

Any tips?

Regards,

Geoff

[mikeporter]

I don't understand what you are seeing. By default Polymorphic VIs are packaged inside the executable like any other VI. are they being configured differently in the build specification? Mike...

[tst · Accepted solution]

Also, check the Advanced page and make sure the 8.x-style check box is unchecked, as this will be checked by default if you imported the project from 8.x and will cause this type of distribution if your VIs are in libraries and have the same file name as other VIs. Be sure to read the help on that check box, as it changes the internal structure of the EXE, which might have implications for you if you're building paths dynamically.

[GeoffF]

Thanks Tst.

Of course!  It was the compatibility mode flag.

Mike: The clue was that I was working mostly in LV8.6.  When using Application Builder with LV 8.6, any polymorphic VIs are packaged separately to the EXE file, as extra files in subdirectories under the EXE's directory.  Thus, you might have:

1. EXE
1. Module1
1. Polymorphic VI1
2. Polymorphic VI2
2. Module2
1. Polymorphic VI1
2. Polymorphic VI2

etc.

Under LV2010, of course, the EXE packaging deals with polymorphic VIs a lot more cleanly.

Regards,

Geoff

[tst]

---

@GeoffF wrote:

When using Application Builder with LV 8.6, any polymorphic VIs are packaged separately to the EXE file, as extra files in subdirectories under the EXE's directory.

---

Again, this has nothing to do with polymorphic VIs. It's VIs in libraries which have the same file name (because LV 8.x saves the files in the EXE as a flat list and you can't have two files with the same name in the same folder).