LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Before installing 7.1 : compatibility

Before installation of a newer version of Labwindows/CVI, I like to know more so I do not have to redo it twice or even more often. I am using version 6.0, and I have just purchased version 7.1.1

The 7.1.1 readme, states that saved UIR-files cannot be read with Labwindows 6.0 or previous. Does this also apply to execatables e.g. do I need to keep version 6.0 if I only want to change details in a UIR-file such as remark-text and colours ?

If installed both versions 6 and 7 (first 6, than 7) the runtime engine will be from the newest version 7. If I make a distribution kit, will it include the newest runtime version as installed, or will it use the runtime that came with compiler, i.e. rte6 when using LW6, and rte7 when using LW7 ?

Regards, Jos
0 Kudos
Message 1 of 5
(3,230 Views)
Jos,

When you build a distribution, CVI will use the version of the runtime that came with *that* version of CVI, not the version that is installed on the system.

I'm not sure I understand your first question completely. You shouldn't need to keep CVI 6.0 around. Both the UI Editor and the runtime are backwards compatible, so you should be able to edit your 6.0 UIRs in 7.1 and also run the application with the CVI 7.1 runtime (regardless of whether you "updgrade" those UIRs or not).

The implication of what the readme says is that if you have co-workers who might still be using CVI 6.0, and you modify the UIRs in 7.1, then they will not be able to view or edit those UIRs using CVI 6.0. If that's not the case, then you shouldn't have to worry about it.

Luis
NI
Message 2 of 5
(3,218 Views)
Hello Luis,

Thanks for the reply.

From your answer, I notice that I did not describe one of my questions clearly.
I make and distribute executables with UIR as separate file in version CVI 6.0. The UIR contains default settings (values in a numerical fields), labels and static text. When a default setting or a static text needs to be updated, I only replace the UIR. This works fine as long as the content in the def-file with the UIR does not change.

So my question is: can an executable made by CVI6, read an UIR that has been updated by CVI7 ?

Regards, Jos
0 Kudos
Message 3 of 5
(3,209 Views)
Okay, I understand your question now.

What matters is not which version of CVI was used to build the executable. What matters is the version of the CVI run-time in the machine which is trying to run the executable. So, if you modify the UIR with version 7, then you will need version 7 or greater of the CVI run-time in order to use the UIR.

Luis
Message 4 of 5
(3,191 Views)
Hello Luis,

Thanks for both replies. It is (I think) fully clear to me now.
For the many people that also took the effort to look at the content of this thread, I will summarize:

I will have to keep working with version CVI6, within projects where I work together with people that also use CVI6.
I can install CVI7 at my computer where CVI6 is already running, but I have to install it in a different subdirectory. (Note that the runtime-engine in the windows-system subdirectory will be replaced with the newest version.) With this CVI7, I can create a distribution kit with the runtime engine from CVI7. If I use CVI6, it will create a distribution kit still with the runtime engine from CVI6.
As the runtime engine is upwards compatible, executables from CVI6 as well as from CVI7 will work fine with the newest runtime engine. So I can make for one computer, executables with either CVI6 or CVI7, provided that this computer has the newest runtime engine.
If I save any UIR with CVI7, I need CVI7 when changing it again, and I need runtime engine from CVI7 at the computer that runs the executable.

Regards, Jos
0 Kudos
Message 5 of 5
(3,183 Views)