NI Labs Toolkits

Showing results for 
Search instead for 
Did you mean: 

Separate Compiled Code for VIs and other files

Mark VIs and other files to Separate Compiled Code tool can be used to mark/unmark a directory hierarchy of VIs and project libraries to separate compiled code from source file. It provides a way to batch convert Files outside the project interface.

System Requirement: LabVIEW 2010 or later

Usage: Place the "SeparateCompiledCode.llb" in your <LabVIEW>/project folder.

After restarting LabVIEW, you will be able to find "Mark VIs Separate Compiled Code..." in your tools menu.

Trusted Enthusiast
Trusted Enthusiast

This can indeed be very useful!

Kind Regards,
Thierry C - CLA, CTA - Staff R&D Engineer, RF Semiconductor Test - National Instruments
If someone helped you, let them know. Mark as solved and/or give a kudo. Smiley Wink
Member SMcGraw

Please download the latest version.  The first version had a bug where it would only mark VIs but not other file types.

Active Participant warren_scott
Active Participant

broken for files inside .llb's

Member SMcGraw

Thank you for reporting this bug.  I've updated the tool so it now works for files inside .llbs

Member Mike_Diesen

Will this funcationality work with LabVIEW 2015?

Member SMcGraw

Yes, this works with 2015.

Member TeraTech

Kudos on the great tool! I am baffled as to why this has not been incorporated into LabVIEW.

Could someone comment on the usage of the tool?  Should I first clear compiled object cache, run the SeparateCompiledCode tool on my top level project folder, then follow it with a  Mass Compile of that folder?

If I now want to copy this folder to another computer: On the destination computer, first do a clear compiled object cache, dopy the vis over, do Mass Compile on the new vis?