I am in general very interested to know of NI's plans to move it's .NET DLLs to .NET Standard such that the DLLs can be run both under .NET Framework and .NET 5 (this is the new name for .NET Core).
I am in particular interested in NI-VISA, since that would be a huge start and seems like it should be the easiest to port. What this would enable is a huge step forward in being able to use other languages with NI hardware. For example, with a .NET Standard NI-VISA DLL, one could use C# or F# on a cRIO running NI Linux Real-Time.
Even better if LabVIEW could call .NET Standard DLLs on Linux.
What NI's strategy to support .NET Standard DLLs and thus .NET 5? This includes releasing .NET Standard DLLs and updating LabVIEW to be able to call and build .NET Standard DLLs.
.NET Core 1.0 was released in 2016, which was six years ago at this point. Given NI has never responded to this question and the fact that I have not seen any mention of .NET Core, .NET 5, or .NET 6 by NI, I can only assume NI has no plans to support anything modern in the .NET world. I was asking NI representatives by phone and email way before I posted this question on the forum, and I don't think they even knew what .NET Core or .NET Standard were or are.
.NET Core is not even called .NET Core anymore. It changed to .NET 5, is now at the current version of .NET 6, and will soon be .NET 7.
.NET Framework, which is all that NI currently supports, will reach End of Support on April 26, 2022. That means it will no longer receive security fixes.
It's very very sad, that there is not even an answer within 2 years for this upcoming problem.
We are in a production company, need to migrate our applications to .NET Core and have the same problem.
Please address this important issue.
Also the IVI Foundation has only outdated libraries.
While a fully .Net core implemented VISA library would of course be nice, that is almost 100% going to be a wet dream. NI is not going to invest very heavily into VISA anymore. What is there is there and works reliably and is maintained but no new development is likely planned for a long time to go.
That all said I'm quite sure even the existing .Net Framework support is mostly simply an Interop library accessing the native VISA32.DLL. Creating a C# Interop wrapper for VISA32.DLL while not trivial to do, definitely is something that would neither require man months of work nor a rocket science diploma. I'm pretty sure there are already some (partial) implementations out there on github or similar.