Allows new functions to be compiled during runtime by using libtcc. http://bellard.org/tcc/
 
Features Full ANSI C compiler  ISO C99 extensions (Missing only complex and imaginary numbers) GNU C extensions (See TCC Docs) TinyCC extensions (See TCC Docs) GNU-like inline assembler  32bit & 64bit opcodes depending on DLL (See TCC Docs) Compile to memory to call as function or disk as exe Allows for dynamic code Pointer safe checks  
Examples
Adding 2 numbers and using return to get the result
Using system to call cmd
Inline x86 assembly
Passing in information using argc and argv
Using pointers to pass a string in and an SHA512 hash out
 
 
Uses libtcc unmodified, so for security reasons you can download the dll from the author's website or compile your own from source. The dll is included if you wish to use it.
 
Some very basic examples that show off only a tiny subset of the features this compiler offers. Unless you are very careful, compiling functions during runtime can lead to unstable code. (Test before you deploy) All examples should run without issue but modification can and will lead to crashing. (Save often)

Name: DCG
Submitter: CopperD
Submitted: 16 Feb 2016
Category: *Uncertified*
LabVIEW Version: Not ApplicableLicense Type: Creative Commons Attribution 3.0



Allows new functions to be compiled during runtime by using libtcc. http://bellard.org/tcc/
 
Features Full ANSI C compiler  ISO C99 extensions (Missing only complex and imaginary numbers) GNU C extensions (See TCC Docs) TinyCC extensions (See TCC Docs) GNU-like inline assembler  32bit & 64bit opcodes depending on DLL (See TCC Docs) Compile to memory to call as function or disk as exe Allows for dynamic code Pointer safe checks  
Examples
Adding 2 numbers and using return to get the result
Using system to call cmd
Inline x86 assembly
Passing in information using argc and argv
Using pointers to pass a string in and an SHA512 hash out
 
 
Uses libtcc unmodified, so for security reasons you can download the dll from the author's website or compile your own from source. The dll is included if you wish to use it.
 
Some very basic examples that show off only a tiny subset of the features this compiler offers. Unless you are very careful, compiling functions during runtime can lead to unstable code. (Test before you deploy) All examples should run without issue but modification can and will lead to crashing. (Save often)

Click here to download this file

Hi all,
 
I have been trying to use VIPM to distribute drivers that rely on a .NET framework that is unsigned (i.e not in the global assembly cache).  My issue is that after the package is installed, none of the VIs will work because LabVIEW cannot locate the .net assembly.  However, if I launch labview by opening the library VIPM installed, all of the VIs will work, and LabVIEW is able to locate the the .Net framework and it appears in the main application instance.  I need to be able to use the installed vis all the time, not just when LabVIEW is launched in this particular way.
 
Here is a link to all the all the files I used: 
 
https://www.dropbox.com/sh/yjt2a0t8msxhgfn/AAC4VVW-hPawwXtGMrZ6wuIra?dl=0
 
Here are the steps I went through:
 
1) We put all the .NET dlls and the LabVIEW.exe.config file in the Labview directory.
 

 
2) We installed the package on our computer.  
 

 
3)We closed everything and relaunched Labview from the start menu.  Then accessed the BioRobotics/Vicon palette.
 

 
4)We placed the Get Ref subVI on the block diagram, opened it up, and ran it it.
 
5) We got the following error:
 

 
We also get a similar error for any VI that uses a method associated with the .NET dll.
 
6) However, if we again start with everything closed and launch Labview by clicking on the VICON.lvlib located in the vi.lib
 

 
7) Then repeat steps 3 and 4.  We do not get any errors in the VIs on the palette, and the .Net assembly loads fine.  We can even close the library and everything still works.  Somehow opening the library first makes LabVIEW know to load the ViconDataStreamSDK_DotNet assembly when using functions on the Vicon palette.
 

 
If anyone does attempt to build a new package, it is worth noting that I included the dlls in the source files, and in the same folder as the vipb:
 

 
 
Thanks!
 
Callan
 

I am trying to export a class in LabVIEW 2013 to a .NET Assembly.  According to this I can just select the members of the class that I want to export and it will generate a .NET class for them.  
 
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/building_a_net_assembly/
 
I am able to export the individual members of the class, but when I run the code in .NET it starts searching for mydllname.dll/myclassname.lvclass (the file of the class that the exported members belong to) and can't find it.  My next step was to add the class to the the Always Included list, but it seems that when I do that some of the members that I have in the Exported VI's list don't show up in the .NET assembly.  The class I'm trying to export is inhereted from another class, so I tried adding both classes to the Always Included list and all of the base class members to the Exported VI's list, but I still have members missing in the .NET classes.  Thinking it could be something releated to exporting LVOOP classes, I tried ditching the LVOOP class altogether and rewrote the labview code to use generic VI's and a cluser typedef to store the member data.  However, it seems like the labview builder doesn't recognize that the control and indicator clusers that I use to pass the member data belong to the same typedef, so it exports a different .NET class for each control and indicator cluster.  This creates a problem because I have no way of passing the output of one funtion to the next in .NET since I cannot convert between the two .NET types.
 
Has anyone had problems like this/know how to fix it???  I couldn't find much online about building a .NET interop assembly beyond the basic configuration steps, so any help would be much appreciated!
 
Thanks

I am trying to open shell32.dll with .NET but an exception is being thrown. I'm seeing this type of exception all over when I search google but really not much related to LabVIEW (mostly vb.net, c#.net etc). I have tried loading shell32.dll from system32/shell32.dll and SysWOW64/shell32.dll and both fail. I am running 32 bit LabVIEW on Windows 7 64 bit. I'm guessing it has something to do with that. I am going to try on a coworkers 32 bit computer when I get a chance, but does anyone have suggestions?
Thanks.
Edit: Tried on 32 bit labview on a 32 bit machine and it still fails.