Does anybody has experience generating DLLs in LabVIEW and using them, for instance, in .NET projects?
I never used LabVIEW generated dlls, I used C++ generated dlls in LabVIE. I thing that this dlls are generated in C code, them they can be used in all software based in C code like .NET projects. Check and see…
LabVIEW works with the DLL file of a program for integrating another language programs with LabVIEW code.
This DLL is generated by writing the Program in Visual C++.It's very easy to create a dll file. you can see the examples already available on the net/google help.
After creating the dll file you can use a function in labVIEW "Call a DLL" by tool menu.
and also you can take help -"http://digital.ni.com/public.nsf/allkb/DCB90714981A1F148625731E00797C33"
thanks for your answers. I also have used DLLs with the call DLL function in LabVIEW. My question refers actually to the opposite procedure, i.e. using DLLs which were generated in LabVIEW in a Visual C++ or C#. I personally conducted some simple tests and it worked, but I still have some problems when using more complex DLLs, specifically to match variable types between my program and my DLL. I'd like to know if someone has experience on this procedure.
I did that for a embedded target with fpga routines. You have to include all the lib paths accordingly within your IDE environment and register the dll within the windows registry. The variables from LV dll come all in specific data structures, here you have convert your stuff accordingly. Best practice is use their structures, create a copy from that in your main routine before handling it down to the dll. In total it's a pain, you have to figure that out for each datatype individually, for me this was the most troublesome, aka googling half a day for each LV datatype. Good luck to you.
Thanks for your answer Dirk. Do you have or remember where to find examples (guides) for the definitions of the specific datatypes? BR.
if the generated DLLs support registration via REGSVR32.EXE tool (it is on the system path so you can run it from the command-line and pass the full filepath to a DLL to it), then they are COM in-process servers in fact (and may also contain/register ActiveX controls [UI elements]). Such servers contain type-information and they register it with the system, so if you use C# and .NET's COMinterop layer, you can easily use them (without needing to import anything manually)
also in Microsoft C++, see the "#import" command that autoimports typeinfo (you don't need to provide the TLB for the typelibrary, it usually is included in the DLL and registered with the windows registry so it know where to find it). Also see the smart pointer operator (->) that handles COM specifics for you when you access some sub-object (like reference counting its usage so that it can self-destroy when it is not needed anymore).
I haven't used LabView in specific, but feel free to ask anymore info, I could look it up for you since I've used COM/ActiveX a lot in the past
Create a new project in .Net and right click on the project and select Add Reference browse your DLLs and them. After adding the DLLs your .Net project showing you the DLLs you have added in your .Net project. Now open your code and do not forget to add the Namespace of the new added DLLs in your coding.
if they do include typeinfo (COM TypeLibrary), you can use the Object Browser of Visual Studio after you've imported them to see their API
if you want you can try uploading such a DLL of yours on Dropbox etc. and share the link here so that I can check it out in Visual Studio and let you know
- Badges
- Science topic
- Similar topics
- Computer Science and Engineering
- Programming Languages