How do you Build an Application DLL when VIs are not in Base Package

[jprucha]

Hi All,

I am using LabVIEW 7.1 and have successfully built a number of applications that we use in a web application/web service and have had no problems building the dlls and calling the exported vis functions.  To this point it has just been the resulting dll that I've put in the web services "bin" directory.  My problem that I have run across is that the current application uses 2 vi's that are not included in the base package (Digital IIR Filter.vi & Sine Waveform.vi in macond.lib & masignal.lib respectively).

From the building an application interface

1.  Do I add these two vi's as dynamic vi's or supported files?

2.  Do I just add their respective lib as a supported file?

3.  Do I have to add all of the sub vi's that are under these two vi's as dynamic or supported?

4.  Then depending on the way I have to do the above which files do I copy over to the web servers bin directory?

Any help would be greatly appreciated.

If you have any questions feel free to let me know.

Thanks in advance,

Jim

[Dennis_Knutson]

What exactly do you mean? If VIs don't exist in the base package and all you have is the base package, how can you be using them to develop an applicaiton? If you have the full version of LabVIEW, then what does it matter that they don't exist in the base version? You create the DLL in the same manner and don't have to call them dynamically.

[smercurio_fc]

I've run into this problem before when using a VI that's in the Advanced Analysis library. Building the DLL resulted in "lvanlys.dll" being copied into the "data" directory of the place where I created the DLL. When distributing the LabVIEW DLL I had created to the target platform I had to also distribute the "lvanlys" DLL. In my case there was no license issue since there was a license for the target machine but it only had the run-time engine installed. I don't know why the "lvanlys" DLL wasn't in the run-time engine install. All I know was that I had to include the "lvanlys" DLL to tag along when I distributed my LabVIEW DLL. I suspect a similar situation is occurring with you and you need to provide these "auxiliary" DLLs if they're not in the run-time install directory of the target machine. You will need to check about any licensing issues though!