Requires: Application Builder or Professional System (Windows)
Use this page of the .NET Interop Assembly Properties dialog box to configure settings to reduce the size of the .NET interop assembly, improve load time, and reduce memory usage when you load the resulting build.
This page includes the following components:
Disconnect type definitions—Specifies whether to omit type definitions from controls during the output of the build process. Selecting this option for an application with a large number of VIs can potentially reduce the memory usage of the build output.
Remove unused polymorphic VI instances—Specifies to remove unused polymorphic VI instances during the build process. When you add an instance of a polymorphic VI to the block diagram of a VI you include in the build, LabVIEW adds all other instances of the polymorphic VI to the build. If you enable this checkbox, the Application Builder removes any polymorphic VI instances you do not call directly from the block diagram. You may want to disable this option if you dynamically load an instance of a polymorphic VI so the Application Builder does not exclude the polymorphic VI instance you dynamically load from the build. Disabling this checkbox may increase the size of your application.
Remove unused members of project libraries—Specifies to remove unused project library members during the build process. If you enable this checkbox, LabVIEW only includes the VIs from the library you call directly from the block diagram. Enabling this option reduces the application size because LabVIEW does not include the other VIs referenced by the same project library unless the VIs are referenced by other VIs that are part of the build.
Modify project library file after removing unused members—If you select to remove unused members of the project library, enable this checkbox to direct LabVIEW to modify the library so that the library file does not refer to the removed members. If you do not modify the project library, the application may take longer to build.
Disconnect unused inline subVIs—If you enable this checkbox, LabVIEW does not load any unused inline subVIs into memory when you load the resulting build, which improves load time and reduces memory usage. LabVIEW considers an inline subVI to be unused if VIs within the build only call the subVI statically via the subVI node. LabVIEW does not disconnect unused inline subVIs unless you disable debugging in the build specification on the Advanced page of the dialog box. You also must remove the block diagrams from unused inline subVIs; otherwise, LabVIEW does not disconnect them.
Note If an unused inline subVI is a member of a class, LabVIEW loads that subVI into memory when you load the build output even if you enable the Disconnect unused inline subVIs checkbox.
Exclude dependent packed libraries—Specifies to reduce the overall number of files in a build output. When you enable this checkbox, LabVIEW excludes copies of dependent packed project libraries to which you link from other build outputs. To exclude dependent packed project library files, LabVIEW retains the links relative to the original dependent packed project libraries instead of copying those files during the build. For example, if you create one build output and then a subsequent build output, you can relatively link the subsequent build output to a file in the first build output. If you leave this checkbox disabled, LabVIEW copies the dependent packed library file to which you linked instead of retaining the relative link to that file.
Exclude dependent shared libraries—Specifies to reduce the overall number of files in a build output. When you enable this checkbox, you limit the number of shared libraries LabVIEW copies. When you create one build output and then link to a file in that build output from another build output, LabVIEW traditionally copies the linked file. To limit the number of copied files, LabVIEW retains the links relative to the original files instead of copying the files during the build.
Note If you move the original files to which multiple build outputs are linked, those outputs may not load correctly depending on the location to which you move the original files.
