difference between development and deployment with test stand from labview

[akonecki]

My question is:

What is the difference between Development and Deployment (i.e. application / executable build) with respect to the TestStand API calls and execution environment from Labview.

I can get the exact behavior I want in development no problem, but I move to a distribution and the test stand engine does not seem to execute my sequences (therefore none of my callbacks ever get called).  All the references appear valid, and the paths are correct for the executable,engine and execution test stand instances say they are executing normally.

Also why does the default behavior of test stand command objects (i.e. buttons) disabled by default along with their inherited behavior.

Thanks,

Andrew

[JimChretz]

When Teststand is configured on Deployment, it will use the LabVIEW run-time engine instead of Development environment. That's the reason why the labview modules become un-editable.

I suggest to read this if you have more questions.

http://digital.ni.com/public.nsf/allkb/EE3382373D209449862570A5006572F0