Possible Caveats running LabVIEW 2017 and NXG side-by-side with LabVIEW 2016

[jwscs]

Hi everyone!

I just recently made a fresh install of OS and LabVIEW 2016 and converted my project to this version.

Now since LabVIEW 2017 is out, i am curious to try it out, but i don't want to "endanger" my development installation.

So, i would like to know if you ran into any problems installing (and running) the new version parallel to your "old" 2016 version, escpecially regarding drivers and in my case needed Real Time Module (for using it with a cRIO-9068).

kind regards and thx for your input

[cbutcher]

Hey,

I've got 2016 and 2017 and NXG installed on my laptop at work, where I run most of the code I write (although I write most of it on a desktop, which has only 201{6,7}). I haven't had any problems yet, but it's only been a short time. I have to be a little careful opening LabVIEW before opening VIs if I want to have a specific version, otherwise I think it defaults to whatever you used last.

One thing to take a little care for is that installing 2017 will upgrade VIPM to the 2017 version, and if you build packages (even for 2016) using the 2017 VIPM, the package won't open on a computer that doesn't have a 2017 version of VIPM (although of course you can still install to 2016 with a 2017 package if that is above the minimum version you built the package for).

I haven't used NXG for anything beyond playing around. I guess it's less likely to collide with anything, but I haven't used it enough to say.

[jwscs]

vipm is a good point i forgot about, i have several additional stuff installed through it (most notably the openG tools).

do i understand you correctly, that the new VIPM will then serve 2017 and 2016 install?

<edit> i don't build packages, so that wouldn't impact me </edit>

[cbutcher]

Yes - VIPM 2017 will happily install packages for an existing 2016 LabVIEW version. It's just that package files you create with it will require a 2017 version to open (including to install). I think many of the packages that people release more widely are typically built with an older version, presumably to allow the widest range of VIPMs to open them. I'm just not sure how to do that - but I only build packages for myself, so it matters far less.

[Blokk]

I have LV2015, 2016, 2017, and NXG 1.0 installed. So far everything works OK.

[billko]

---

@cbutcher wrote:

Yes - VIPM 2017 will happily install packages for an existing 2016 LabVIEW version. It's just that package files you create with it will require a 2017 version to open (including to install). I think many of the packages that people release more widely are typically built with an older version, presumably to allow the widest range of VIPMs to open them. I'm just not sure how to do that - but I only build packages for myself, so it matters far less.

---

You have to have that earlier version of LabVIEW, as VIPM will want to open it.

If you built a package in a newer version of LabVIEW and want to make it available in an older version, I believe the accepted (only?) way to do it is to actually save the project for that earlier version and build!

[JÞB]

I am having no trouble running 2016, 2017 and NXG1.0 side by side.  The Tools network is doing great and all the TKs I use install successfully.

TK List:

Viewpoint TSVN 

Darren's Hidden Gems

LAVA CCT

I did require an upgrade to TSVN (Now on 1.9.5 YEAH! I needed that anyhow)

[jwscs]

thank you guys for the input!!!

[jwscs]

just as a reference in case someone finds this post

http://forums.ni.com/t5/LabVIEW/There-may-be-a-problem-installing-LabVIEW-2017-quot-on-top-of/td-p/3...