NI software compatibility related questions

[TeaAndBiscuits]

Q1.
Does NI guarranty that multiple LabVIEW EXEs (based upon related multiple run-time engines) wun simultaneuosly ono the same Windows XP computer, flawlessly?
If no, what are constraints ?
ex.
LabVIEW EXE application built with version 7.1
LabVIEW EXE application built with version 8.2
LabVIEW EXE application built with version 6.1
LabVIEW EXE application built with version 8.6
all at the same time ?
I am aware it works in some applications, but does NI guarranty it will always be so under Windows XP?
How about Vista?

Q2. As an NI customer for several years, is it legal to have copies of many versions of labVIEW development environment on the same computer at the same time?
I am aware it works at least on machine, but is it legal ?

Q3. Is LabVIEW really platform independent ? What are the constraints that must be considered when porting a LabVIEW application between Windows to Linux or MAC?
Not looking for whole list but application design wise ?
some key bulletpoints may be helpful on top of some document links.

Q4.  I have a  software EXE program that uses API calls from VISA sandard. If I upgrade my NIMAX, will it replace VISA library that my EXE was using ?
In either case, will it affect working of my EXE ? If it does affect, How to go about avoiding this. My EXE may want to use old VISa calls for years.

[muks]

---

Q2. As an NI customer for several years, is it legal to have copies of many versions of labVIEW development environment on the same computer at the same time?
I am aware it works at least on machine, but is it legal ?

---

I feel it is absolutely legal to have multiple registered versions on the same machine

[TCPlomp · Accepted solution]

---

Sandeepvd wrote:

Q1.
Does NI guarranty that multiple LabVIEW EXEs (based upon related multiple run-time engines) wun simultaneuosly ono the same Windows XP computer, flawlessly?

I'm not sure it works flawlessy, but it shouldn't be a problem. Make sure you don't access the same resources (hardware, tcp ports etc)

Q3. Is LabVIEW really platform independent ? What are the constraints that must be considered when porting a LabVIEW application between Windows to Linux or MAC?

Yes they should be portable, however front panel's might need to be redesigned. Also daqmx is limited on linux/mac. No activex or .net. When dealing with dll's and you have a compatible linux/mac library, make sure the extension is not specified in the VI calling the DLL and have them in the same folder (have a look at the daqmx VIs for an example of this)

Q4.  I have a  software EXE program that uses API calls from VISA sandard. If I upgrade my NIMAX, will it replace VISA library that my EXE was using ?
In either case, will it affect working of my EXE ? If it does affect, How to go about avoiding this. My EXE may want to use old VISa calls for years.

---

I doubt it that VISA will be modified AND not be backwards compatible,I have never had an issue with this.

Ton

[Mark_Yedinak]

I have never run into an issue having multiple versions of the run-time engine installed and working on a single computer. We run like this all the time. Also, VISA will only install the latest version and in my experience it has worked with executables built using older versions of VISA.

It is my understanding that your license allows you to use the version you purchased and all prior versions of LabVIEW. You should confirm this with NI though.