Is there a new version of Labwindows 2023 planned?

[MarcelK]

---

@Slateman wrote:

My main usage case of labwindows/cvi is creating headless DLLs that work with TestStand (Teststand pulls in the parameters automatically due to the 'special' CVI linker which makes development a lot easier). No other linker/linker settings have that capability...

---

If that refers to the feature that TestStand automatically knows the parameter names and types of a DLL call, a DLL equipped with a standard Type Library (from .idl file) does the same trick. Used that with Visual Studio a few times, just a bit more work creating the idl file.

[pistino]

Question: If Emerson/National Instruments is no longer interested in releasing updates or new versions of LabWindows/CVI, why not make this product free and open source?

[carlox]

@pistino
What you don't know is that LabWindows likely exists as a product only because of the multi-year supply and maintenance contracts with US government and military entities. For the same reason, it's not even conceivable that it will be released open source.
My recent conclusion is that this is ultimately a good thing. LabWindows is an old, dated project that uses a programming model from the 1990s, if not earlier. It's definitely time to migrate to something more modern and functional, and rehashing old code isn't the way to go.
This is just my opinion, of course.

[FRANKFRANKFRANK]

Maybe it is time to discussion what is replacement or experience for new software solution ?

That is more important than guess NI if new release;

Py

C

Cpp

C#

MATLAB

 and other

[Xavier9905]

Hello LabWindows/CVI Community,

We understand that many of you have questions about the future of LabWindows/CVI, and we want to reassure you of our commitment to the product. Therefore, we plan to release LabWindows/CVI 2026 in the coming year.

Please see this forum post for additional information. Please reply to the linked post for questions and comments or feel free to message me directly.

Thank you,

Xavier

[paul.knight@zeroavia.com]

This is good news.   I am a Manufacturing Test Engineer and have use C++, C#, Pascal, Python, MATLAB, BASIC, and LabWindows\CVI to program Manufacturing Test on the Production floor.  There is no contest of which is the better language to do my job in, LabWindows wins hands down.