LabVIEW 2024 insists on converting project version on every launch

[Mads]

Having just installed LabVIEW 2024Q3 on a clean machine I opened an old project (saved in 2022, which is what I have been using up until now) and set the project to save as 2024 and saved. Unexpectedly though, every time I opened the project after that, it still says the project version has been changed and must be saved...

So, in an attempt to get around this, I did a save for previous version of the project, and saved as 2024. I then opened the resulting project (which should now have its entire hierarchy saved in 2024...), but the project *still* insists on having been converted to 2024 from version 0.0?0  (!) on every open/close.

What is going on? The change explanation looks like this:

Saving does not return any errors and none of the files are locked, so there should not be any save issues in any case. Am I doing something wrong, or is this the intended behaviour (in which case it act as a bug...)?

[Kyle97330]

I mean, a "lvproj" project file is just XML.

If you open it Notepad or your favorite text editor, does anything look weird?  Specifically, the line containing the version? 

I have LabVIEW 2021, which looks like:

<Project Type="Project" LVVersion="21008000">

I assume 2024 should be similar.  If yours is somehow mangled, perhaps it's different and it confuses LabVIEW?

[Mads]

Partly. The LVVersion has for some reason after being opened in LabVIEW 2024 gone to "0". Here is the kicker though; if I open it and save it the LVVersion key is corrected. The header then looks like this:

<?xml version='1.0' encoding='UTF-8'?>
<Project Type="Project" LVVersion="24008000">
<Property Name="CCSymbols" Type="Str">IsClient,True;FixedSetupFolder,False;</Property>
<Property Name="NI.LV.All.SaveVersion" Type="Str">24.0</Property>

but the next time it is opened LabVIEW still insists on it having to be converted and saved, and when that happens it resets the LVVersion to 0 again (!):

<?xml version='1.0'?>
<Project Type="Project" LVVersion="0">
<Property Name="CCSymbols" Type="Str">IsClient,True;FixedSetupFolder,False;</Property>
<Property Name="NI.LV.All.SaveVersion" Type="Str">24.0</Property>

So the LVVersion *is* changed by LabVIEW 2024Q3, but it forces it to alternate between 0 and the correct  24008000 entry.

Manually editing the XML entry instead messes thing quite well up, all kinds of VIs show up as missing afterwards although they are still in the same location.

Creating a new project from scratch is so far the only solution. Some kind of bug in the project conversion process from 2022 to 2024, but it is not like that in general: I tried converting a different project to 2024 (opened it, set the save version of the project to 2024 and saved) and that works as expected so there is some quircky way the conversion of some projects can go wrong it seems.

[crossrulz]

---

@Mads wrote:

Creating a new project from scratch is so far the only solution. Some kind of bug in the project conversion process from 2022 to 2024, but it is not like that in general: I tried converting a different project to 2024 (opened it, set the save version of the project to 2024 and saved) and that works as expected so there is some quircky way the conversion of some projects can go wrong it seems.

---

I was going to suggest checking the project save version. Maybe try setting it to 2023, save all, and then to 2024 and save all again. It might also not hurt to clear the compile object cache and then mass compile the project.