TestStand missing dependencies on VI that runs correctly in LabVIEW

[JoseRivero]

Hello, title is my assumption of what is happening. Here is the situation. 

I am dealing with packed libraries containing classes to provide hardware abstraction. One VI being used is the protected Load LV Default Class.vi. While the packed library being loaded goes through this VI without problems when using only LabVIEW Development, this same VI outputs error 1498 (library has errors) from TestStand. 

The library does not have code errors but could be having problems finding some dependencies that LabVIEW does find (.NET DLLs used within library methods/overrides).

Is there a magic TestStand setting to prevent this behavior. How come all checks out if running from LabVIEW , but as soon as TS is fired up all linkages get lost? 

This is more of a general TS behavior question, don't have actual code to share. I am using  LV2018, TS2017, 64-bit, using LV Development in the adapter setting (not the runtime, yet!)

Any ideas?

[JoseRivero]

Update: 

Was able to make it run if the VI setting in TS is changed to "always use the RT engine". Still puzzles why? Normally it is the deployment running Runtime that misses some dependencies, not the Development. I have yet to deploy this. 

Anyhow, would like to read of any logical explanation for the initial posted question.