Welcome to the LabVIEW Public Beta Program in 2024!

[Christina_R]

Note: this post is about the "first" Beta in 2024, which used the released LabVIEW 2024 Q1. The "second" phase of the Beta uses the LabVIEW 2024 Q3 Beta.

Installation

This Beta is different than in past years. Although we are using the Beta forum to gather feedback, the functionality is in the released LabVIEW 2024 Q1, and can be enabled with configuration tokens. Note that these Preview features are not supported features of LabVIEW 2024 Q1 and are Beta quality.  

You will need to install LabVIEW 2024 Q1 to participate in this Beta. You can use the Evaluation version or the Community Edition if you want to provide feedback without purchasing a subscription to LabVIEW.

New Features

• Developing a LabVIEW Project in an Older Save Version File Format
• Modified Algorithm for Compare VIs (“Diff”)

Thank you for your participation! I look forward to seeing your feedback. 

[Ray.R]

Thanks Christina!

It is great to "see" you and to participate in the Beta Program.

Wishing you a fantastic 2024 to you and all your loved ones.

RayR

[Albert.Geven]

Thanks Christina

But I can only find a community edition for 2023 Q3, probably in a few days?

[Mads]

A beta *after* the release...that's a new one 🤔

First experience with the update so far: when you download the fresh 2024 installer the NI Package Manager that comes with it is already outdated(!). So if you are installing on a clean machine you have to abort the install at a point, restart the now just installed NI Package Manager version, update it, and then restart the initial installation. Not particularly smooth...

[Christina_R]

---

@Albert.Geven wrote:

But I can only find a community edition for 2023 Q3, probably in a few days?

---

Yes, sorry, Community Edition is still being published. I'll post an update when it's available!

[WesW]

---

@Mads wrote:

...

First experience with the update so far: when you download the fresh 2024 installer the NI Package Manager that comes with it is already outdated(!). So if you are installing on a clean machine you have to abort the install at a point, restart the now just installed NI Package Manager version, update it, and then restart the initial installation. Not particularly smooth...

---

I can confirm that the NI Package Manager included in LV 2024 is already the latest version and will automatically install, so that's probably not the issue. Was it a dialog like the following that you saw?

If so, what's happening is that since 2023 Q2, Package Manager updates the Microsoft .NET Framework to 4.8 if the system is not already at that version. Unfortunately, that .NET update can sometimes put the system in a state that a reboot is needed before any further installation can be done. Though annoying, this is just what the Microsoft .NET update requires. But the majority of systems have this version (or newer) of .NET already, the reboot is only necessary sometimes, and it's a one-time update - so it's not seen frequently. Do reply back if you saw something different!

[Mads]

No this was a dialog from a volume license installer I created from the 2024 Q1 Embedded and control suite offline package that said that with the options I had chosen to install the process had to be aborted due to the need for an update of the NI Package Manager (prior to this the machine had no NI software at all). I aborted and opened the Package Manager which then showed the usual link in the upper left corner saying an update was available. Having run that update I could proceed with the VLM install.

[WesW]

---

@Mads wrote:

No this was a dialog from a volume license installer I created from the 2024 Q1 Embedded and control suite offline package that said that with the options I had chosen to install the process had to be aborted due to the need for an update of the NI Package Manager (prior to this the machine had no NI software at all). I aborted and opened the Package Manager which then showed the usual link in the upper left corner saying an update was available. Having run that update I could proceed with the VLM install.

---

Gotcha! Yes, this is an issue with VLM, that the version of NIPM installed on your VLM machine is what is used to create the VL installer (VLI). This works fine, except if the product you are including in the VLI is built with a newer NIPM version (like LV 2024), then you see this mismatch error.

The workaround is to first update NIPM to the latest version on the machine building the VLI, then all VLIs created on that machine will be using the latest NIPM - which will avoid the problem. We hope to improve this experience in the future by warning you at VLI build time of this mismatch so that you can be aware of the situation before rolling it out.

Sorry you ran into this issue!

[Christina_R]

---

@Albert.Geven wrote:

Thanks Christina

But I can only find a community edition for 2023 Q3, probably in a few days?

---

The Community Edition of LabVIEW 2024 Q1 is now available!

[altenbach]

---

@Christina_R wrote:
The Community Edition of LabVIEW 2024 Q1 is now available!

---

I beg to differ..... 😞