Company Events Academic Community Support Solutions Products & Services Contact NI MyNI

Caveats and Recommendations for Separating Compiled Code from VIs

LabVIEW 2011 Help

Edition Date: June 2011

Part Number: 371361H-01

»View Product Info
Download Help (Windows Only)

The following list describes some of the caveats and recommendations to consider when you separate VIs from compiled code:

  • You cannot save Express VIs and simulation diagrams without compiled code.
  • The LabVIEW Run-Time Engine has no access to the VI object cache. Do not separate compiled code from a VI that runs on the Run-Time Engine. If you intend for VI hierarchies that you check into source control to run on the Run-Time Engine, build a source distribution with the VIs.
    Note  Do not place a checkmark in the Remove compiled code checkbox on the Additional Exclusions page of the Source Distribution Properties dialog box if you intend to run the source distribution in the LabVIEW Run-Time Engine.
  • If you receive VIs with separate compiled code from another user, LabVIEW requires time to compile the VIs and generate their VI object files on first load because those object files did not previously exist on the computer.
  • VIs must have either a block diagram or compiled code to load. Do not separate compiled code from VIs without block diagrams.
    Note  VIs saved without a block diagram in a previous version of LabVIEW cannot recompile. Verify the version number in the Source version text box on the General page of the VI Properties dialog box.


Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
Add Comments 1 2 3 4 5 submit