LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
TSherry

.net function box

Status: New

.net calls can end up being pretty verbose in LabVIEW, having to pipe between property boxes to get to some nested value, when the call is pretty straightforward when written in a more traditional language. In addition, trying to replicate some .dll functionality seen in c++ is frustrated by how different the calls look. Having the ability to drop into a function block to write .net code would make it much easier to port functionality + debug.

Even if there was a penalty performance wise, it would still be a nice middle ground for getting a prototype off the ground before optimising it for LabVIEW.

1 Comment
wiebe@CARYA
Knight of NI

This would be a C# function box then?

 

 

Spoiler

Doable, even for us (non-NI). The function node structure is 'somewhat open', and .NET has a build in C# compiler. The trick would be to let them play well together, the C# code needs to be compiled to a dll or exe.