labwindows 5 compatibility with recent CVI2015

[HussainHTS]

Hello,

we have all the source code written in CVI 5.0, i would like to upgrade to very recent one like CVI 2015,  will i have any compatobility issues? 

1) if we modify source code & create object files in CVI 2015 verison can it be used in test PC which has CVI 5.0 ? (I have test stand even its source is compiled in CVI 5.0) 

thanks

Hussain

[mkossmann]

If you code followed strictly the C-standart, there should be no problem. But in real-world code you have a grey zone with contructs, which aren't covered by the standart and may work differently with another compiler version. 

And according to http://digital.ni.com/public.nsf/allkb/3FA3982EBA12B3D286256896005FAA39  there is no OS version which is supported by both compiler versions. To run CVI code to have to install a verion  of CVI runtime, which supports the compiler, which created the code.

[RobertoBozzolo]

It is difficult to answer such a question: it depends on the functions you are using in your program (some CVI functions have changed or have been deprecated since CVI5.5), on the external libraries you may be needeing which may be not compatible with newer OSs or CVI IDEs...

Nevertheless, upgrading your IDE is highly recommended in my opinion to gain native support for modern operating systems, to be able to use new controls and functions added in the meanwhile, to gain better support option both from NI and from forum users (I remember to have answered some questions of yours but such an old CVI version makes me hard to remember what I could use in 5.5 and I no more have a machine with it). Be warned that this may be a one-direction move: it you happen to upgrade your UIR files, even if no modern controls are added you won't be able to open them in 5.5; additionally, some code changes may be needed that cannot be ported back to 5.5.

The best option is to install an evaluation copy of CVI2015 on a different machine (so the original development machine is not affected, e.g. by the change in the CVI Run-time) and try compiling the code.