support for calling .net6 assemblies in LabView

[NetDev]

In the current documentation there is only a description how to call the classical .net framework assemblies.

6 years ago, Microsoft released the first version of .netcore which now has evolved into .net5, .net6 or soon .net7.

Microsoft has announced years ago, that this is gonna be the future path of the .net framework development.

Does anybody know of any plans of National Instruments to support the modern .net assemblies to call within LabView?

[rolfk · Accepted solution]

Yes it is in the LabVIEW Roadmap https://forums.ni.com/t5/LabVIEW/LabVIEW-Roadmap-2022/td-p/4218319.

Not in the next 2 releases, so do not hold your breath. It will be at least LabVIEW 2023 before you can hope for that.

[NetDev]

Well, this is not the answer i was expecting/hoping. Sad to see that NI needs more than 5 years to keep up with the actual technology...

[rolfk]

I'm sure all the resources for .Net development were put into LabVIEW NXG. It was after all supposed to be based heavily on .Net under the hood. With that gone, focus has moved back to LabVIEW Classic, but adopting such a fundamental change like moving from .Net Framework to .Net Core is not an over the night job! Especially since calling old Framework assemblies needs to keep working exactly as before for backwards compatibility.

[nottilie]

I know this is a rather old entry but it think it is time to refresh.

@Rolf "now there are again gone almost two years" so we waited many "Overnights" to have any new statement than in the roadmap from 2023

where it is stated as "future releases"

Does anybody know if it will ever happen that .NET now 7 or 8 will be supported.

The communication of Emerson on progress is more than conservative.

In the meantime I really worry that they will drop Labview completely as in the last years there were not too much communication or really outstanding improvements. (Since they dropped NXG)

[JensFu]

Since it does not seem that Emerson is supporting anything in this direction, we resigned and go with a workaround of a Python Wrapper.

So LabView calls Python, and Python calls .net6.

This is a desperate and nasty solution, but maybe it helps others.

[Yamaeda]

Wrappers and proxies are common, i wouldn't call that a nasty solution, but a solution.