We are upgrading our code base from LabVIEW 2016 to LabVIEW 2018. I expect to see about 6500 vis and ctrls being saved. In Perforce I have checked out our source code repository, In LV2018 opened up the projects and vis that pull our whole project in to memory and save all. Then in perforce I use "revert unchanged" so as to not check in random text files and the like. It ends up reverting about 2/3 of our source code repository because there was no change on disk. In years past (e.g. LabVIEW 2012> LabView 2014 > LabVIEW 2016) we have used this method and it has touched every vi in our source code repository. Has something changed such that LabVIEW 2018 doesn't need to change the file when reading LabVIEW 2016 vi's? I thought at a minimum it would have written a "saved in LV2018" flag to it.

I'm going to go ahead and bet that if you looked, all of the unchanged VIs have the common trait that they have the "Separate compiled code from source file" option checked and the VIs themselves are simple enough that nothing was altered in them in the last 2 editions. I don't have 2016 but I confirmed that a VI saved in 2015 and loaded in 2018 doesn't get the dot if it has that option enabled, and does get the dot if that option is turned off.

LabVIEW

LabVIEW 2018 not changing vis (no dirty dot) when upgrading from LabVIEW 2016

Solved!

There is a free utility that would have saved you a lot of time. It allows searching and sorting your entire project by 42 Vi properties including Separate Compiled Code, VI Modified and LabVIEW Version. Just search your project for LabVIEW Version less than 18, select all and then choose File -> Save Selected. DONE.

http://free.propinsp.com

Michael Munroe, CLD, CTD, MCP
Automate 1M+ VI Search, Sort and Edit operations with Property Inspector 5.0, now with a new Interactive Window Manager!
Now supports full project automation using one-click custom macros or CLI.