Patching LabVIEW VIs

When you create a patch deployment for a test system that uses LabVIEW VIs, consider the following issues:

• Removing files from an LLB, packed project library, project library, or a project and creating a patch deployment might negatively affect sequence files or VIs in the existing deployed test system. To ensure compatibility, only add—do not delete—files to an LLB, packed project library, project library or project.
• If you do remove files from an LLB, verify that previous deployments do not require the files. Do not manually remove unchanged code module VIs from the source files. Instead, rely on the TestStand Deployment Utility to remove files that do not differ from the previous deployable image.
• The deployment utility automatically processes VIs by updating links to subVIs and other dependencies to ensure the VIs can execute without errors when run using the LabVIEW Run-Time Engine on a test station computer without the LabVIEW development system installed. Do not use a patch deployment to replace a VI with an unprocessed VI because doing so can break the VI because of missing dependencies or broken links to dependencies. Instead, make the changes to the source VIs and rely on the deployment utility to process the files and include required files in the patch deployable image.