Hi
'Project/Library Save Version' sounds like a simple thing, but it is far from being simple.
So, I have tried to follow the development of this new concept, basically to answer the two questions :
- 'what can it really be used for' and
- 'when can it not be used'.
There was a beta phase throughout 2024 where many issues were discussed and addressed.
But I still have the following outstanding questions :
¤ Is this feature officially to be referred to as 'Project/Library Save Version'. An official concept name is useful in order to get the best hits in a Google search.
¤ Are there situations where it is necessary to have two LabVIEW versions installed to be able to use 'Project/Library Save Version'. I hope not.
¤ Does the new LabVIEW ( say 2025 ) version, used for editing older LabVIEW code ( say 2020 ), need to have installed all the drivers, toolkits and modules, as present in the older LabVIEW version. If yes, how is discontinued toolkits and modules handled. And discontinued hardware support in drivers.
¤ Has NI or somebody else written a Tutorial or a White Paper about this new feature. Kind of 'where are we now' reflecting paper.
I have followed the very interesting multi-page thread, but it kind of stopped early 2025 :
https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/Preview-Feature-in-LabVIEW-2024-Q1-Developin...
Christina Rogers made a four sections write-up late 2024 :
https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Beta-Feature-Developing-VIs-that-Can-Be-...
Anyone know 'where we are now' ?
Regards
