Automated LabView version cross saving

[Andi_S]

Situation:

  I have to support several production lines which are using different LabView versions (currently LV 8.5.1 and LV 2009). On my office PC I would like to use always the latest LabView.

  If I open a project which was created in LV 2009 in a newer version of LabView, LV will try to convert all files to the new version. If I transfer it back to a PC which uses LV 2009 I can not open it.

Suggestion:

  I'd like to suggest a new project parameter that changes to storage format of all the files contained in the certain project (excluding those coming out of the LV program folder and maybe from some other excluded folders).

[AristosQueue (NI)]

Beginning in LV 2011, there is an option in the VI Properties called "Separate compiled code from source file." You enable it on all your VIs. Then when you open them in the later version, LV doesn't need to force the file itself into the latest version. Of course, if you actually edit and save the VIs, then they're committed to the new version and you'll have to use File >> Save For Previous. But if you're just opening and using them, this is a major savings.

[smercurio_fc]

There is also the practical matter of features. Some features simply don't exist in previous versions. Is LabVIEW supposed to disable those features? Are you suggesting that same parameter in the project file is used so that LabVIEW knows to disable certain things (similar to the Target Framework parameter for Visual Studio solutions)?

Similar ideas:

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Compile-for-Previous-version/idi-p/1123893

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Save-for-previous-version-should-warn-about-incompatib...

[Andi_S]

Yes, I think that's the only way it make sense. LabView needs to disable the incompatible features (or at least it must warn if somebody tries to use such  features).

Aditionally LabView should ask in case that somebody opens an old project if it should be converted or if the user wants to go on programming in LabView XX mode with disabled new features. If the user selects the second option the cross-saving parameter should be set to the old LV version so that he will not be asked every time again.

[Andi_S]

@ smercurio_fc

Of course, this idea could and should be included:

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Compile-for-Previous-version/idi-p/1123893

If a project is set e.g. to LV 2009 the buils (DLL, EXE, ..) should also be executable on a LV 2009 RTE.