LV8 coexisting with previous versions

[kevintho]

I was wondering if anyone has had any experience yet with LV8 being installed on a machine co-existent with previous versions of LV. Since now that LV8 will seemingly have better project orientation and structure, how will that effect currently organized projects in other versions, particularly while coexistent on the same computer? Are there any discovered "gotcha's"?

In other words, can we expect LV8 to play nice with its older siblings in the same house, so to speak...

Yet another concern is for coexistent add-on tools and tool-kits, libraries, modules (e.g. vision, motion, DAQ, etc.).

This is not really a question about upgrading LV, (NI details published in "Upgrade Notes"), but rather a concern regarding coexistence during a methodical or slow migration (or in some cases, perhaps no migration).

Any early thoughts, comments, concerns, or suggestions?

Thanks,

Kevin Thompson

[Rolf Kalbermatter]

I was wondering if anyone has had any experience yet with LV8 being installed on a machine co-existent with previous versions of LV. Since now that LV8 will seemingly have better project orientation and structure, how will that effect currently organized projects in other versions, particularly while coexistent on the same computer? Are there any discovered "gotcha's"?

In other words, can we expect LV8 to play nice with its older siblings in the same house, so to speak...

Yet another concern is for coexistent add-on tools and tool-kits, libraries, modules (e.g. vision, motion, DAQ, etc.).

This is not really a question about upgrading LV, (NI details published in "Upgrade Notes"), but rather a concern regarding coexistence during a methodical or slow migration (or in some cases, perhaps no migration).

Any early thoughts, comments, concerns, or suggestions?

Thanks,

Kevin Thompson

LabVIEW itself has been always a nice citizen as far as undesired interaction with other installations on the same machine is concerned. I do not expect any difference with LabVIEW 8 unless the packagers at NI somehow messed up and built a bug in the installer.

With add-on toolkits it is sometimes a different story. All native LabVIEW add-on toolkits should be fine but others such as IMAQ can be a bit problematic in certain cases. You may sometimes need to install certain bug fixes and definitely allow the Toolkit installer to also install compatibility VIs for older LabVIEW version into their respective directory.

With drivers you have to be carefull to allow the driver installation (for instance NI-DAQ) to upgrade the (DAQ) VIs in the older LabVIEW systems, to sometimes allow them to continue to work with the new driver.

These last two points where a Toolkit or driver for LabVIEW version X may also include VI libraries for LabVIEW version X-1,2,.. installations requires however that the older LabVIEW version is already installed on the system. Installing older versions of LabVIEW after newer versions is not a very good idea.

Rolf Kalbermatter