Care to expand on this? I have not ran into any problems with it yet. There are a few programs I have yet to port over.
Nothing specific and mainly some minor problems.
My Labview experience can differ a lot and maybe be less relevant for your software but I am sure you can judge that by yourself.
Main problem I have had was poor compatibility with
Keysight IO Libraries VISA software if it also should coexist with NiMax. I as well as some other users of my software had problems with this compatibility that not seldom ended with total breakdown and reinstall of both NI-VISA and Keysight drivers, which in later versions of Labview can take several hours to first remove and then reinstall using by NI provided tools.
Maybe was my problems specific for my NI installation but Keysight VISA driver compatibility have had some compatibility problems, at least since Labview 6.1.
Keysight VISA driver need a rather big software installation of Keysight "IO Libraries" installed because it is a need if using Keysight USB-GPIB adapters. There are possibilities to just include a minor driver library for Keysight VISA adapters but it is driver installation at hacker level.
I remained long time using Labview 8.5. It fulfilled my and my customer needs. Never versions do not add any bells or whistles that not can be created in 8.5 from software view and programming environment is downgraded in some aspects from my view.
Main reason that I switched to newer version was that Labview 8.5 not was compatible with newer version of Nimax and some customer had for other reasons updated to newer version of Labview runtime including Nimax so it was a must to update if i wanted compatibility with newer versions of Labview runtime.
It is else not any absolute must to use Nimax, there are other possibilities to communicate with instruments, but as my software intend to be compatible with all brands and models of VNA as long as they talk GPIB/IEEE-422 is my software self configuring for each type of VNA, is it very practical and comfortable from programming view when Nimax is working properly. One problem less to handle and even if it is problems can that be solved without affecting my software code.
It is then instead a problem for actual VNA manufacturer to provide a NI-VISA-compatible driver and proper IEEE-422 communication but most commercial VNA's have a such interface.
Nimax and windows file properties are the both sources that have cost most problems for my customers as well as needing my support. I have actually done a bit half dirty programing to automatically elevate my software properties during some file operations, such as dynamically saving settings in ini-files located in ordinary program directory or automatically download and replace existing exe-version, which else may need administrator rights.
Since I reverted to Labview 2020-32 from 64-bit have I not had any known problem with Nimax or compatibility with Keysight soft and hardwares.
Porting software between different versions of Labview is seldom any big problem.
As long as you have highest version of Labview installed can that version save for compatibility with lower versions as well as importing older versions. Some functions that have disappeared in never version or can need some cleanup of the code as well as when saving for older versions. It is seldom any problem, both older and newer versions of Labview runtime can coexist and it is possible to include code for both version when writing a new vi.file. Drawback if mixing several runtime versions is that if you distribute that file to others do they also need several runtime versions installed.
One such common case is for example when read/write spreadsheet files which file functions differ between older and newer Labview versions.
Had a minor problem as I had code that was upgraded to 64-bit and afterwards continued developed. Then did I replace 64 bit Labview with 32-bit and couldn't any longer open the 64-bit version of my vi-file. Had to install a virtual 64-bit version just to be able to save this file for older 32 bit version.
Have not tested it but a file compiled for 64 bit Labview environment do probably refuse to run using 32-bit Labview runtime.
It is possible that both 64 bit and 32 bit environment can be installed in parallel as they not use same program directories but have not tried. Do not want to add another possible source to problem.
Have else full environment of several older Labview versions installed. That is not any problem except for that older labview versions not can use newer versions of NI-488 and NI-VISA.
Partly list for which versions that are compatible can be found here:
https://www.ni.com/sv-se/support/documentation/compatibility/16/ni-visa-and-labview-version-compatibility.htmlI have a list for older labview versions as well, if needed.