How TestStand Deployment Utility determines the LabVIEW version to build?

[Ajay_MV]

I am trying to build a packed library from a .tsd file (TestStand utility file).  I built using TestStand 2017, but the built packed library is LV2018 (I can see in build log as below that build occured in the LabVIEW 2015). 

I couldn't find in LabVIEW options under deployment utility for any LabVIEW version selection.

TestStand is also selected with Auto selection for RunTime engine and NO selection given for LabVIEW Development System

[Ajay_MV · Accepted solution]

Found it...!

The Active LabVIEW version determines it.  If I have LV2015 opened and trigger the build, then TSD can pack in LV2015.  If any later version is opened (like 2018 in my case), then TSD packs in that version.

So, for my continuous integration, it's important to load the desired LabVIEW version first before triggering the build in TestStand Deployment.

--

Thanks

AJ

[Ajay_MV]

Recently I noticed that usage of version selector resets this setting.  I had to activate the adapter in TestStand to LabVIEW 2015 development environment to fix.  

--

Thanks,

Ajay

[Ajay_MV]

The recently loaded LabVIEW version determines this.

Steps to build in desired LabVIEW version.

1. Close all LabVIEW. 
2. Open the desired LabVIEW  Version (2015 or 2018)
3. Then open the TestStand Deployment Utility (never open the TSD before loading desired LabVIEW)