From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
09-19-2022 02:43 AM
I did a quick search for this, but didn't find anything. Apologies if this has been addressed before, but I couldn't find it.
With the new LabVIEW naming scheme, how do we know which versions of code are natively compatible with the IDE?
For example, recently SP releases would happen around March. Previously that release would be called LV2022 SP1 and code could be opened from vanilla LV2022 and vice versa without any need to save for previous version. With the new names, that would be called 2023 Q1 instead. Is that code natively compatible with 2022 Q3? Where's the cutoff for VI compatibility between versions?
Solved! Go to Solution.
09-19-2022 08:35 AM
The general plan is to have releases in the same year (ex 2023 Q1 and 2023 Q3) be binary compatible.
Quoting somebody from NI in a private board: "Yes, we intend for Q3 release to be "binary compatible" with Q1 and install into the same folder, but if it needs to be a "breaking" release then it will install into a separate folder, e.g., C:\Program Files\National Instruments\LabVIEW 2023 Q3."
09-19-2022 09:13 AM
Thanks. So is 2022 Q3 all by its lonesome or is it compatible with 2021 SP1 since it came out in the same calendar year?
@crossrulz wrote:
The general plan is to have releases in the same year (ex 2023 Q1 and 2023 Q3) be binary compatible.
Quoting somebody from NI in a private board: "Yes, we intend for Q3 release to be "binary compatible" with Q1 and install into the same folder, but if it needs to be a "breaking" release then it will install into a separate folder
There's no way this will ever get confusing... 😛
09-19-2022 09:29 AM
@CaseyM wrote:
Thanks. So is 2022 Q3 all by its lonesome or is it compatible with 2021 SP1 since it came out in the same calendar year?
I'm under the impression it will be all by its lonesome. But we shall see.
09-19-2022 04:56 PM
My understanding is that the binary compatibility will be associated with version year, not the calendar year. So:
2021 and 2021 SP1 - binary compatible
2022 Q3 - special snowflake
2023 Q1 and 2023 Q3 - binary compatible
2024 Q1 and 2024 Q3 - binary compatible
...
With the possible exception that a breaking change in a version year will install to a separate folder, as mentioned above. I expect the chance of this happening to be quite low.
09-19-2022 05:01 PM
09-19-2022 05:07 PM
That I don't know (I'm not in R&D anymore). My impression (again, not official word) is that feature scope will be appropriately sized for regular 6-month releases, so the whole 'SP1 will mainly have bug fixes' paradigm is no longer accurate.
But I could be wrong.