When you make changes to an assembly while that assembly is in memory, you must force LabVIEW to reload the assembly in order to access the changes. Complete the following steps to force LabVIEW to load changes to an assembly.
Note An assembly remains in memory even if you delete all nodes that reference the assembly from the VI.
Identify the name, version number, and path on disk of the assembly that you changed.
Use the .NET Assemblies in Memory dialog box to identify all LabVIEW projects that have a version of the modified assembly in memory. For each project that uses the assembly, verify that the version number and path of the assembly in memory match the version number and path of the assembly that you changed. If this information does not match, LabVIEW is using a different copy of the assembly than the one you updated. You can debug the assembly call to make LabVIEW load the correct assembly.
Close and reopen all projects that reference the modified assembly.
Note If a VI in the main application instance references the modified assembly, you must relaunch LabVIEW in order to access the changes. National Instruments strongly recommends that you use .NET objects only in LabVIEW projects.
