Have you ever had a situation, when some old project was accidentally opened in newer LabVIEW, and was resaved to that higher version? Of course, if you use software version control like git or SVN - then it is not a problem, because you can simply reset your working branch to previous state. But what if meanwhile you've implemented some changes, and after that re-saved all the project? It's a pity because after rollback, all those changes should be implemented again. And in case when project is stored outside git or SVN repository, then the situation is even worth...
So if you had such a situation at least once, then I believe this small tool could be useful for you.
When LabVIEW project is opened, this tool checks version of the project. If it is implemented in lower LabVIEW version than the active one (by active I mean LabVIEW version in which you open a project) - then you'll recieve warning window about it. After that, you could close project and do not save it. Or if you've opened project in higher LabVIEW version intentionally, you can continue working with the code, and then save it as you wish.
It does not check versions of opened LabVIEW VIs, libraries, classes, etc. Main reason - it will be not practical at all. Many reusable libraries/toolkits are implemented in the lowest possible/useful LabVIEW version, so then they are mass-compiled when added to the actual code. And it would be quite bothering to see every time some warning window while opening such VIs.
This toolkit is compatible with LabVIEW 2015 and higher, Windows OS. It has just a little of functionallity, but I will be very happy for any type of feedback/contribution. Please feel free to post issues, ideas, or do fixes/improvements of the code. List of used software: LabVIEW 2015 SP1, Caraya Unit Test Framework v1.1.0.119, VIPM 2020.3.