Separate compiled code from VI together with TestStand LabVIEW runtime engine

[Mattias_Ericsson]

Hi,

Question, is it possible to have "separated compiled code from soruce VI" in any VI for a LabVIEW test used in TestStand when using LabVIEW Runtime engine option for the LabVIEW adapter?

Am I forced to deselect "Separate Compiled Code from Source VIs" for all my test VIs (including subVIs and vi.lib VIs?). I've notice in LV2011 beta that all VIs in vi.lib have "Separate Compiled Code from Source VIs" enabled (that differs from LV2010 where all is deselected in vi.lib). If any VIs can't have separated compiled code option selected (including vi.lib), then how could I use LabVIEW Run-time engine option for the LabVIEW adapter if vi.lib settings will change in future versions of LabVIEW?

Regards,

Mattias

[RayFarmer]

Mattias,

I think you should have posted this in the LabVIEW beta forum, even though it relates to TestStand, you may find you have breached the beta rules by posting here.

[Mattias_Ericsson]

Hi, this feature is actually lv2010, but they just changed the default setting in lv2011. You could use separate compiled code in lv2010, thereby my question in this forum. However, I have tried and it works just fine to use separate compiled code with runtime engine in TestStand. It seems as TestStand do some preanalysis and compile of the code before executing. I used Ts2010.