Does the definition of "Execution State" equals "Bad" change between development environment and run-time?

[Retamoza_R]

Hi all,

Did you manage to find a good way to do this without having to add every single dinamically loaded VI in the "Always included" section of the build? I'm kind of having the same problem and, while I can include all the VI's and their subVI's, it wouldn't be practical.

Also, do you know of any way of using Execution.state to check the state of an executable from another executable? Sorry to bring another different topic in but it's kinda' related.

[Patrick_NI]

Hello Akatora, 

To answer your first question, it should be possible to dynamically call a VI without always including it.  For more information please see this KnowledgeBase:

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9fiSAC&l=en-US

As far as your other question, yes it is possible.  Please see the following example:

https://forums.ni.com/t5/Example-Code/View-All-VI-s-in-Memory-and-Their-Execution-State/ta-p/3505468

This example can be built into an executable which will tell you all VIs in memory and thier execuation state.