11-28-2016 06:53 AM
Is it advisable to have professional development system LabVIEW 2016 32 bit and LabVIEW 2014 32 bit versions on the same machines? And if OK any risks to take into consideration?
11-28-2016 07:01 AM
The only real concern is drivers. I am pretty sure the 2016 drivers will work with LabVIEW 2014. But is that the version of drivers you want to develop with in LabVIEW 2014?
The other issue is making sure you are developing in the correct version of LabVIEW for your project.
In short, I recommend using a Virtual Machine if you are going to be using multiple versions of LabVIEW for project development. That way you can keep all of the 2014 code in a VM with the 2014 drivers, etc and all of the 2016 code and drivers in another VM.
11-28-2016 07:25 AM
I've had as many as 5 versions of LabVIEW on my main work machine, and eventually "paid the price", did a "Remove all", and a more limited re-install [though I have to confess that I currently have 2012, 2014, 2015, and 2016 on here -- 2011 has been "banished" to a VM].
Here are some elements to consider:
I'm in agreement with Crossrulz. In order of "safety", the safest way to go is to use a single Version on your PC. The next-safest is to have "single-Version VMs" (but not everyone can work with VMs). If you are careful, however, you can usually "get away with" having multiple versions of LabVIEW on your Development machine -- just take precautions (of which I think the most important is using Version Control, as it allows you to "go back to before I stupidly saved as the newer Version").
Bob Schor
11-28-2016 08:21 AM
Thank you both for very informative response. Much appreciated.