06-02-2009 01:08 AM
chrisger,
I have checked the h. file
This looks like the exthample but only one declared function ( maine VI name ) present ther .
Does it mean that all vereables can be contloled by customer's aplication?
06-02-2009 10:37 AM
If you want to export more than just the main.vi the answer is "no".
Once again, check the function prototypes of your VIs in the dll's build specification. Take a look at the documentation by clicking "Help" on the build specification dialog box to learn more about building DLLs.
08-10-2010 07:25 PM
I have followed most of the steps with ease, and understand the code & VI's, but I have a couple of questions regarding how to build the dll in this example.
1. How do I use the 'build script for dll.bld' file to generate the Sharedlib.dll in a LabVIEW project, I am using LabVIEW 2009 SP1 Professional Development System. I have made efforts to generate my own Shareddll.dll but unsure what settings you have in your build process. eg C style or Std function calls...
2. Should I then copy the dll to the C#.NET bin\debug folder for use?
Background: In my project I am trying to get C#.NET to modify the value of a LabVIEW global variable, so that Labview VI's can be controlled from the external C#.NET application. (My Lavbiew Project attached)