We have a large application that calls modules dynamically. It has been working in LV 8.2. We compile the main program and use "Source Distributions" to distribute modules for individual installations. Thus these modules are LV source code in directories that the .exe calls dynamically. Two of our modules use DAQMX, so the distributions get understandably large. Since the DAQMX is an option that most customers don't use, we incorportated a Conditional Disable structure around them and used a custom Conditional Disable key. We set this key's value in the project before creating the source distribution, so that we can choose whether or not the DAQMX sub-vis are included in the distribution. This all worked fine in LV 8.2. We recently upgraded to 8.6. Now the distribution includes the DAQMX sub-vis regardless of the conditional key. I thought that maybe the condition got "disconnected" in the upgrade process, so I created a new key, deleted and replaced the conditional disable structure, but to no avail. Worse than just having the sub-vi's included in the distribution, even though they have been supposedly removed, the fact is that if the DAQMX drivers are not loaded on the target machine, the VI is broken and won't run. Even though the VIs aren't using the DAQMX sub-vi's, they are broken because the associated dll's are missing. I looked through the forums, and though I found a number of messages about the Conditional Disable, I couldn't find anything specific about this issue. Is this a known issue? Is there a work around?DaveT

LabVIEW

conditional disable no longer works

Hi Folks,

I just got back from NI Week 2010. I attended a couple of sessions that discuss a new feature that basically resolves the issues described in this thread. This is the Packed Project Library.

A Packed Project Library is a compiled library target available as a new build target in LV 2010. Because it is compiled it is limited to the platform it was compiled for. It is accesable through VI Server. And the conditional disables are processed so that unused code is removed from the compiled target.

I think this solves all the issues discussed in this thread. I haven't had a chance to try it though.