How LabVIEW Reports Outdated References to .NET Framework Assemblies

If you load a VI referencing a .NET Framework assembly that has since been changed, LabVIEW notifies you. The type of notification depends on the nature of the change.

Note The following content applies to .NET Framework only. LabVIEW has been gradually adding support for .NET (Core) since LabVIEW 2024 Q3. Refer to LabVIEW New Features and Changes for specific .NET (Core) support added in different releases.

Microsoft Visual Studio .NET and other development tools provided in the .NET SDK can assign strong names to an assembly. Strong names include additional information beyond the simple text name of the assembly. Assemblies with the same strong name are expected to be identical.

When you load a VI that references a .NET Framework assembly that has since been changed, LabVIEW notifies you about the issue in the following ways.

Table 51. LabVIEW Notifications in VIs Referencing Changed .NET Framework Assemblies
Type of Reference Behavior
Load a VI with an outdated reference to either of the following:
  • Path of a .NET assembly
  • Version number or culture string of a strong-named assembly
 LabVIEW launches a warning dialog box informing you of the change.

Once loaded, the VI includes an asterisk in its title bar and in the list of open VIs displayed in the Window menu.

When you save the VI, the asterisk disappears until you make a new change.
Load a VI with an outdated reference to the time stamp of a .NET Framework assembly LabVIEW does not launch a warning dialog box but does display an asterisk in the title bar of the VI.
Tip You can verify that LabVIEW is loading the version of your assembly that you expect. For more information, refer to Debugging Calls to .NET Framework Assemblies.