Prevent silent conversion of vi's/projects/libraries to new labview version

[Labuser16383]

I created some libraries (.lvlib and .llb) for own use wth 2013, then accidently used them in lv 2015 vi's which i saved then.

however when i recognized this and wanted to open the libraries in 2013 again they could not be opened anymore.

labview just silently converted the libraries to the new version and did not warn me about this behaviour.

Is there a way to prevent this behaviour and at least get a warning about the conversion between versions?

After that issue i tried to save back the libs to lv 2013 which again caused problems, because instead of simply overwriting

the contained vi's with the 2015 stamp replacing them with versions with a 2013 stamp

it always wants to create a completely new directory structure which again breaks the dependencies.

at this point i started to regret wrapping vi's into libraries at all instead of simply using the single vis.

So there is the second question: Any way to save back the libraries to 2013 preserving the original directory structure?

[GerdW]

Hi Lab,

which i saved then. … did not warn me about this behaviour.

Well, you had to acknowledge that save dialog. And you had the chance to read why you are enforced to save!

It wasn't that silent and you got a warning!

Any way to save back the libraries to 2013 preserving the original directory structure?

Well, that's the point where you should think about some kind of source code control (aka SVN or GIT). They are very nice tools to go back to older versions without hassle…

You surely have backups of all your important data (read: "source code") so just pick a backup with those LV2013 VIs!

[mikeporter]

There is also an options setting about not asking to change "automatic" changes -- like recompiles. You want to set a configuration setting that causes read-only files to be treated as locked. Then set the VIs as read-only.

Mike...

[Labuser16383]

Thank you, i found that option. Up to now, thanks to version control, i was at least able to get the 2015 vis running again.

So the situation is becoming better again.

However i don't understand why the "treat read only vis as locked" should prevent that version conversion issue i had.

I saved the vis with strg-s and i did not get any feedback to acknowledge save so i still feel my post was reasoned.

[mikeporter]

The treat read-only VIs as locked just helps prevent spurious saves in general by warning you if you try to modify a read only file.

Mike...