In LabVIEW 2010 or later, you can separate compiled code from a VI.

When you open a VI with separate compiled code, LabVIEW generates and saves a VI object file (.viobj) with the compiled code.

When you separate compiled code from a VI, recompiling the code of the VI does not create an unsaved change. As a result, if you use a source code control system, you do not have to check out all the files in a hierarchy when you edit a VI.

TestStand supports calling these VIs from LabVIEW. During deployment, the TestStand Deployment Utility converts these VIs with separated compiled code to regular VIs so that TestStand can execute these VIs using the LabVIEW Run-Time Engine on the deployed machine.