TestStand loading LabVIEW code with "separate compile code" ticked

[danny_t]

Hi,

I think I know the answer but thought I'd ask anyway to check.

I am playing around with TestStand and an exciting LabVIEW project. I am running TestStand 2017 and LabVIEW 2018. I have on all my VI the "separate compile code" option ticked and my adapter configuration is set to use LabVIEW 2018 development system and not runtime.

I have a mixture of source versions of LabVIEW some being LabVIEW 2010. These will not load into TestStand.  I see TestStand 2017 is only compatible back to LabVIEW 2013. 

I suppose I am surprised that with my complied code cache being created in LabVIEW 2018 that this is a problem.

Is this expected behavior ?

[crossrulz]

I find it interesting since all TestStand should care about it that LabVIEW 2018 is opening the file.  What if you go ahead and mass compile the VIs?  Perhaps that will fix the issue.

[danny_t]

I'm currently doing  a mass compile will take a bit of time to complete though and if it works I will have a huge commit on my source control branch unfortunately.  I was just hoping to avoid that pain. 

In the LabVIEW world it all fine working with the old VI's just a recompile on load.

[EDIT] Mass compile now complete and it all works fine.