CVI 8.5 Change Compatibility Mode

[nakrul]

Hi,

when CVI 8.1 was started for the first time a panel popped up showing that the compatibility mode is being changed. When starting CVI 8.5 this panel is not popping up and the files that were created during the compatibility mode are not available. How can I solve this problem ?

Steven

[JonathanN]

Hi Steven,

What is the exact problem that you are having (i.e. are you getting errors at run-time?).  We did make a few changes to what happens when you change the compatibility mode in the Options >> Build Options dialog but that shouldn't have affected your applications at all.

If you are having issues, please let me know what they exactly are.

Thanks

Best Regards,

[nakrul]

Hi Jonathan,

the compatibility mode I mean is not the compatibility mode in the Options >> Build Options dialog. It is the small popup firing up the first time you start CVI. The second time you start CVI the compatibility mode was already changed and the popup does not appear any more. The compatibility mode change creates for example the lib files in the extlib directory in the CVI81 directory.  The lib files are missing in the extlib directory of CVI85 and my Visual Studio projects link against these files.

Best Regards,

Steven H.

[JonathanN]

Hi Steven,

The Compatiblity with option found in the Options » Build Options dialog is what is responsible for that pop-up occurring in versions prior to CVI 8.5.  This is clearly indicated by the fact that when you are in the Build Options dialog and you change that field, a dialog appears stating "Changes made to the compatibility mode setting take effect the next time you run CVI".

Now in versions prior to CVI 8.5, lets say that you changed that field to Visual C/C++. This meant that when you launched CVI again, a pop-up would occur telling you that we were changing the compatibility mode which under the hood meant that we would copy the libraries from <CVI>\extlib\msvc to one directory above it at <CVI>\extlib\.  In versions 8.5 and later, we don't copy those files over but rather CVI at run-time knows which libraries to link against so users from the CVI perspective won't have any problems.

In your case, you will have a problem but the solution is easy which is simply to set your linker settings to point to the <CVI>\extlib\msvc directory.   

Just so you know, because of this change, we did update the LabWindows/CVI Project and Conversion Wizards to know where to link against. So another option for you might be to run that Conversion Wizard on a "empty" project and see what settings we configure for include paths and linker paths.

Hope this helps!

Best Regards,