Does Upgrading from LabVIEW 2017 to 2017 SP1 Force a Recompile?

Updated May 3, 2018

Reported In

Software

  • LabVIEW 2017 Base
  • LabVIEW 2017 Full
  • LabVIEW 2017 Professional
  • LabVIEW 2017 SP1 Base
  • LabVIEW 2017 SP1 Full
  • LabVIEW 2017 SP1 Professional

Issue Details

I want to upgrade from LabVIEW 2017 to 2017 SP1. I am using shared files that have to be recompiled in the event of a version upgrade. Does an upgrade from 2017 to 2017 SP1 force a recompile of existing VIs compiled in 2017 or does it only upgrade the development environment?

Solution

LabVIEW 2017 and 2017 SP1 use the same compiler, so you will not need to recompile shared files created in 2017 if you upgrade. A VI created in 2017 will not have a dirty dot (indicating that VI needs to be recompiled/saved) when opened in 2017 SP1 and vice versa. The differences between 2017 and 2017 SP1 are bug fixes and added features in the environment.

Additional Information

See LabVIEW Release Details for further information on upgrading and known issues.

WAS THIS ARTICLE HELPFUL?

Not Helpful